BBS in a Box 7/BBS in a Box - Macintosh - Volume VII (BBS in a Box) (January 1993).iso/Files/MacTechNotes/MacTN files by date

Text File | 1992-11-16 | 216KB | 4,144 lines

 Name  =  Absolute Pointing Device.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Absolute Pointing Device.cpt
 Size: 13K         Date:10/30/92         Version:
 Description:
 This Technical Note specifies a memory data structure for use by absolute
pointing devices; it was developed for the Apple Desktop Bus (ADB) but
could also be used for devices using serial input. Generally, this data
structure is created and updated by the pointing device’s driver and read
by either an application or the system cursor rendering software.

 Name  =  ZoomWindow.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:ZoomWindow.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 ZoomWindow - This Technical Note contains some hints about using
_ZoomWindow. Changes since February 1990. Fixed a bug in DoWZoom which
caused crashes if the content of a window did not intersect with any
device’s gdRect.  Also made DoWZoom more robust by making savePort a local
variable and checking for off-screen and inactive GDevice records.  (One
variable name has changed.)  Additional minor changes:  Corrected original
sample code to use _EraseRect before zooming and added references to Human
Interface Note #7, Who’s Zooming Whom? for more subtle and application-
specific considerations.

 Name  =  X25 & X400 Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:X25 & X400 Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 X25 & X400 Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Worldwide Ov Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Worldwide Ov Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Worldwide Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  WordTemp-21.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:WordTemp-21.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 WordTemp-21 - The routines SetupA5 and RestoreA5 do not work properly when
used with some optimizing Pascal and C compilers.  Two new routines,
SetCurrentA5 and SetA5, are available in MPW 3.0, and they should work with
any compiler. Changes since December 1988. Removed the sample code and
expanded the explanation of these two routines. The sample code in
Technical Note #180 reflects these new A5 routines.

 Name  =  WordBreak Tables.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:WordBreak Tables.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 WordBreak Tables - This technical note describes how to construct auxiliary
break tables for use with the FindWord routine in the Script Manager.

 Name  =  Window Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Window Mgr Q&As.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Window Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Which File System is Active.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Which File System is Active.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Which File System is Active - This Technical Note discusses how to
determine which file system a particular volume is running. Changes since
June 1990. Removed text about IDs $0001-$0016 being AppleShare volumes;
other file systems use this range too. Under certain circumstances it is
necessary to determine which file system is currently running on a
particular volume.  For example, on a 64K ROM machine, your application
(i.e., especially disk recovery utilities or disk editors, etc.) may need
to check for MFS versus HFS.  Note that this is usually not necessary,
because all ROMs, except the original 64K ROMs, include HFS.

 Name  =  WaitNextEvent Bug in 1.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:WaitNextEvent Bug in 1.0.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 WaitNextEvent Bug in 1.0 - This Technical Note discusses a bug in
WaitNextEvent in MultiFinder 1.0. This bug only occurs when WaitNextEvent
is called from the background. This bug will be fixed in the next release
of MultiFinder. Change since 11/87 the bug will be fixed in Systems with
versions greater than $04FF.

 Name  =  WMgrPort.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:WMgrPort.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 WMgrPort - Where WMgrPort (the Window Manager’s port), MultiFinder, and
drawing outside of one’s windows will be reconciled.

 Name  =  WDs & MultiFinder.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:WDs & MultiFinder.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 WDs & MultiFinder - This technical note describes the way that working
directories are handled under MultiFinder. Some versions of Technical Note
#77 claim that you can open working directories with a unique ioWDProcID
and that they will only be deallocated when “the system is rebooted.”

 Name  =  WDEF and wDraw.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:WDEF and wDraw.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 WDEF and wDraw - This Technical Note explains why custom window definition
functions may not respond to a wDraw message from the system (if you follow
the documentation in Inside Macintosh).

 Name  =  Volume Handling Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Volume Handling Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Volume Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Virtual User Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Virtual User Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Virtual User Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Virtual Memory Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:Virtual Memory Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Virtual Memory Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Video Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Video Q&As.cpt
 Size: 17K         Date:10/29/92         Version:
 Description:
 Video Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Version Territory.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Version Territory.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Version Territory - This Technical Note describes the 'vers' resource
supported by Finder 6.1 and later. Changes since April 1989. Changed MPW C
code to reflect the changes in MPW C 3.1.

 Name  =  VIA Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:VIA Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 VIA Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  VCBs and Drive Numbers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:VCBs and Drive Numbers.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 VCBs and Drive Numbers - The top of page IV-178 in The File Manager chapter
of Inside Macintosh in attempts to explain the behavior of two fields in a
volume control block when the corresponding disk is offline or ejected. Due
to the fact that a little bit is left unsaid, this paragraph is rather
misleading. The two fields in question are vcbDrvNum and vcbDRefNum
(referred to as ioVDrvInfo and ioVDRefNum in C and Pascal). PBHGetVInfo can
be used to access these fields.

 Name  =  Using RegisterName.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Using RegisterName.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Using RegisterName - The verify flag indicator byte (verifyFlag) of the
AppleTalk RegisterName function should always be set TRUE in published
code.

 Name  =  User Items in Dialogs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:User Items in Dialogs.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 User Items in Dialogs - The Dialog Manager does not go into detail about
how to manage user items in dialogs; this Technical Note describes the
process. Changes since March 1, 1988. Added MPW C 3.0 code, added a
_SetPort call to the Pascal example, and noted the necessity and meaning of
enabled items.

 Name  =  Update Perils.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Update Perils.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 Update Perils - This Technical Note discusses potential problems when
pending update events for windows behind modal dialogs are not serviced.
This note also documents some new System 7 Dialog Manager calls.
Changes since August 1991:  Added note clarifying how to use the new calls,
documented use of StdFilterProc in Interface.o,and corrected code errors.

 Name  =  TrueType Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TrueType Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 TrueType Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Toolbox Karma.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Toolbox Karma.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Toolbox Karma - This Technical Note discusses Macintosh Toolbox
compatibility and what you can do to help the Macintosh continue evolving
in the future.

 Name  =  TokenTlk Pgm Gd Update.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:TokenTlk Pgm Gd Update.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 TokenTlk Pgm Gd Update - This Technical Note presents the additions and
changes to the TokenTalk Programmer’s Guide and the latest information with
regard to software development for the Apple Token Ring NB and Token Ring
4/16 NB network cards.

 Name  =  Token Ring Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Token Ring Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Token Ring Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Title Index.cpt
 Path =  AMUG CD:Files:MacTechNotes: Indexes:Title Index.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Title Index - This index lists each Tech Note by Title, and gives the
corresponding designation.

 Name  =  Time Space and CopyBits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Time Space and CopyBits.cpt
 Size: 21K         Date:10/29/92         Version:
 Description:
 Time Space and CopyBits - This Technical Note describes the various factors
that can influence the speed of _CopyBits so that developers can set up
conditions to achieve the best performance for the particular situation.

 Name  =  TextEdit Technicalities.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit Technicalities.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 TextEdit Technicalities - This Technical Note discusses some areas in
TextEdit that have not previously been clearly documented. Changes since
February 1990. Added a note about the changes in TextEdit for System
Software 6.0.5, documented the low-memory global TESysJust, clarified
information about text direction and _TESetJust, discussed problems with
the SetWordBreak routine along with a solution to work around it, and
described the differences in dialog text item behavior.

 Name  =  TextEdit Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit Q&As.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 TextEdit Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  TextEdit Limits Again.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit Limits Again.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 TextEdit Limits Again - This Technical Note describes another limit on the
length of a TextEdit record that was previously undocumented.

 Name  =  TextEdit EOL Ambiguity.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit EOL Ambiguity.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 TextEdit EOL Ambiguity - TESetSelect may be used to position the insertion
point at the end of a line. There is an ambiguity, though; should the
insertion point appear at the end of the preceding line or the start of the
following one? It is possible to determine what will happen, as you are
about to see.

 Name  =  TextEdit Conversion.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit Conversion.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 TextEdit Conversion - Text sometimes must be converted between a Pascal
string and “pure” text in a handle. This note illustrates a way to do this
using MPW Pascal.

 Name  =  TextEdit Bugs in 4.2.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit Bugs in 4.2.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 TextEdit Bugs in 4.2 - This note formerly described the known bugs with the
version of Styled TextEdit that was provided with System 4.1. Many of these
bugs were fixed in System 4.2. This updated Technical Note describes the
remaining known problems.

 Name  =  TextEdit.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TextEdit.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 TextEdit - This technical note will point out some bugs (and possible
workarounds), and other items of interest for the TextEdit programmer.

 Name  =  Tags.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Tags.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Tags - Apple has decided to eliminate support for file-system tags on its
future products; this technical note explains this decision. Some of
Apple’s disk products (and some third-party products) have the ability to
store 532 bytes per sector, instead of the normal 512. Twelve of the extra
bytes are used to store redundant file system information, known as “tags”,
to be used by a scavenging utility to reconstruct damaged disks.

 Name  =  TEScroll Bug.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:TEScroll Bug.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 TEScroll Bug - A bug in TextEdit causes the following problem: a call to
TEScroll with no horizontal or vertical displacement (that is, both dh and
dv set to zero) results in disappearance of the insertion point.

 Name  =  System S/W Util Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:System S/W Util Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 System S/W Util Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  System Error 33.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:System Error 33.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 System Error 33 - System 3.2 introduced a new system error, ID=33,
generated by the Memory Manager when it notices that a heap had been
corrupted in a certain way. This error is listed in the file “SysErr.a” as
“negZcbFreeErr”.

 Name  =  Swapping MMU Mode.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:Swapping MMU Mode.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Swapping MMU Mode - This Technical Note describes how to avoid crashing
when swapping into 32-bit mode on a Macintosh II.  Thanks to Jim Berry and
Dan Weston for pointing this out. Changes since April 1989. Added a
reference to Technical Note #213, _StripAddress:  The Untold Story.

 Name  =  Surprises in LW Driver 5.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Surprises in LW Driver 5.0.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Surprises in LW Driver 5.0 - This Technical Note describes some changes in
version 5.0 and later LaserWriter drivers. Changes since April 1988.
Described a bug in 5.x which is fixed in 6.0 and later, and reiterated a
warning about storing fonts in an application. With the release of
LaserWriter 5.0 and background printing, a few changes had to be made to
the LaserWriter driver.  Although these changes were transparent to most
applications, some have had problems.  Most of these problems are related
to use of unsupported features. This Note details a partial list of the
changes.

 Name  =  Subject Index.cpt
 Path =  AMUG CD:Files:MacTechNotes: Indexes:Subject Index.cpt
 Size: 32K         Date:10/29/92         Version:
 Description:
 Subject Index - This index expounds upon each of the topics covered in
Technical Notes.

 Name  =  Sub(Launching) H-L Langu.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:Sub(Launching) H-L Langu.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Sub(Launching) H-L Langu - This Technical Note discusses the “safest”
method of calling _Launch from a high-level language that supports inline
assembly language with the option of launching or sublaunching another
application.

 Name  =  Styled Text Edit in 6.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Styled Text Edit in 6.0.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Styled Text Edit in 6.0 - Some changes were made to TextEdit in System 6.0
to provide more functionality and to make life easier for the programmer
using TextEdit.  This Note documents those changes and enhancements.
Changes since August 1988. Corrected an error in TEDispatchRec in the
figure on page 8.

 Name  =  Strip _OpenResFile/_Open.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Strip _OpenResFile/_Open.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Strip _OpenResFile/_Open - This Technical Note discusses a bug in
_OpenResFile and _OpenRFPerm which can cause system crashes and what you
can do to avoid this problem.

 Name  =  _StripAddress.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:_StripAddress.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 _StripAddress - Inside Macintosh, Volume V, The OS Utilities, incorrectly
documents the _StripAddress trap; this Technical Note correctly documents
the trap and gives guidelines for its use. Changes since April 1990. Added
a discussion of why the _StripAddress trap should be used under certain
circumstances when patching traps.

 Name  =  Stationery Pads.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Stationery Pads.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Stationery Pads - With the introduction of AppleShare (Apple’s file server)
there are restrictions on self-modification of application resource files
and the placement of configuration files. This note describes one way to
get around the necessity for configuration files.

 Name  =  Start Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Operating System:Start Mgr Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Start Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Standard File Tips.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Standard File Tips.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Standard File Tips - SFSaveDisk and CurDirStore. Low-memory location $214
(SFSaveDisk—a word) contains –1* the vRefNum of the volume that SF is
displaying (MFS and HFS). It never contains –1* a WDRefNum. Low-memory
location $398 (CurDirStore—a long word) contains the dirID of the directory
that SF is displaying (HFS only). This information can be particularly
useful at hook time, when the vRefNum field of the reply record has not yet
been filled in.

 Name  =  Standard File Pkg Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Standard File Pkg Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Standard File Pkg Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Standard File Customization.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Standard File Customization.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Standard File Customization - This note contains an example program that
demonstrates how SFPGetFile can be customized using the dialog hook and
file filter functions. SFPGetFile’s dialog hook function and file filter
function enable you to customize SFPGetFile’s behavior to fit the needs of
your application.

 Name  =  Stand-Alone Code.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Stand-Alone Code.cpt
 Size:113K         Date:10/29/92         Version:
 Description:
 Stand-Alone Code - This Technical Note discusses many of the issues related
to stand-alone code modules.  This Note is by no means a completely
original work, as the author borrows freely from the work of Keith Rollin,
Mark Baumwell, and Jim Friedlander. Changes since October 1989. Completely
rewritten to broaden the discussion of stand-alone code modules and include
a greater scope of examples.  Incorporates Technical Notes #110, MPW.
Writing Stand-Alone Code and #145, Debugger FKEY.

 Name  =  Spool/Print Shared.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Spool/Print Shared.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Spool/Print Shared - This technical note discusses drawbacks of using the
spool-a-page/ print-a-page method of printing.

 Name  =  Speedy Coprocessor.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Speedy Coprocessor.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 Speedy Coprocessor - This Technical Note presents an overview of the 68881
and 68882 math coprocessors, and it covers general information about the
chips as well as how using the chips directly can help speed your
math–intensive code.

 Name  =  Spare A Block.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Spare A Block.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Spare A Block - This Technical Note discusses a new feature of the System
Software 7.0 Disk Initialization Package—bad block sparing.

 Name  =  Space Aliens (ADB) .cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Space Aliens (ADB) .cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Space Aliens (ADB) - This Technical Note explains how the Apple Desktop Bus
(ADB) works on the Macintosh.  This Note covers the boot process, driver
installation, ADB Manager run-time behavior, use of ADB Manager calls, and
answers commonly asked questions. Changes since February 1990. Added
description of the boot process to include detail on how the ADBS resource
gets called by the System, added detail to 2 of the answers in the Q&A
section, and added sample completion routines for the ADBOp function.

 Name  =  SourceRoutes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:SourceRoutes.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 SourceRoutes - This Technical Note discusses source routing and its
possible implementation in token ring link layers.

 Name  =  Sound Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Sound Mgr Q&As.cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 Sound Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Sound Input Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Sound Input Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Sound Input Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Sorting.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Sorting.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Sorting - This technical note describes how to modify the standard string
comparison by constructing an itl2 resource. Developers may want to modify
the standard string comparison if Apple’s comparison doesn’t meet their
needs or if Apple has not written a string comparison routine for the
language that concerns them.

 Name  =  Sony Drives For You.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Sony Drives For You.cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 Sony Drives For You - This Technical Note discusses the Sony driver control
and status calls that are available on the Macintosh. Changes since April
1990, Corrected Figure 2, since the Return Physical Drive Icon (csCode =
21) returns an error message instead of an icon on the Macintosh Plus.

 Name  =  Smear Tactics.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Smear Tactics.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Smear Tactics - This Technical Note discusses a feature of the current
Macintosh hardware which will not be supported in the future. Macintosh
hardware developers and driver writers should be aware of this limitation
as it affects current and future products.

 Name  =  Slot Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Slot Mgr Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Slot Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Slot Interrupt Priority.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Slot Interrupt Priority.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Slot Interrupt Priority - This Technical Note describes the way interrupt
priorities are scheduled, which corrects the description of slot interrupt
queue priorities in the Device Manager chapter of Inside Macintosh, Volume
V-426.

 Name  =  Signals.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Signals.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Signals - Signals are a form of intra-program interrupt which can greatly
aid clean, inexpensive error trapping in stack frame intensive languages. A
program may invoke the Signal procedure and immediately return to the last
invocation of CatchSignal, including the complete stack frame state at that
point.

 Name  =  Setting and Restoring A5.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Setting and Restoring A5.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Setting and Restoring A5 - The routines SetupA5 and RestoreA5 do not work
properly when used with some optimizing Pascal and C compilers. Two new
routines, SetCurrentA5 and SetA5, are available in MPW 3.0, and they should
work with any compiler. Changes since December 1988. Removed the sample
code and expanded the explanation of these two routines. The sample code in
M.TB.MultifinderMisc reflects these new A5 routines.

 Name  =  SetLineWidth Revealed.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:SetLineWidth Revealed.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 SetLineWidth Revealed - This technical note describes the internal
implementation, and correct method of using, the SetLineWidth Picture
Comment. The SetLineWidth picture comment provides a way of accessing
PostScript’s 'setlinewidth' operator. Since the LaserWriter resolution is
roughly four times that of the Macintosh screen, fractional line widths can
be printed. The SetLineWidth PicComment provides a way for applications to
access these fractional line widths through PostScript, without having to
use floating point numbers.

 Name  =  Servers on AppleTalk.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Servers on AppleTalk.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Servers on AppleTalk - Many applications could benefit from the ability to
share common data between several Macintoshes, without requiring a file
server. This technical note discusses one technique for managing this
AppleTalk communication.

 Name  =  Serial H/W Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Serial H/W Q&As.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Serial H/W Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Serial GPi The Reliable Way.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Serial GPi The Reliable Way.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Serial GPi The Reliable Way - This Technical Note discusses the latest
supported methods for reading, validating, and configuring the GPi serial
input across all members of the Macintosh family. GPi is a software
configurable serial input present on some machines. It is located at pin 7
on the DIN-8 serial connectors, and connects to the DCD input of the Z8530
Serial Communications Controller (SCC). Because DCD is monopolized by the
mouse on the Macintosh Plus, GPi is not implemented on that machine. Other
machines which do not support GPi include the Macintosh Classic and Mac LC.
On these machines, pins 7 of the DIN-8 serial connectors are not connected.

 Name  =  Serial Driver Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Serial Driver Q&As.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Serial Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Separate Resource Files.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Separate Resource Files.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Separate Resource Files - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Sense Lines.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Sense Lines.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Sense Lines - Ever wonder how to set up an Apple video card or an on-board
video to support various size monitors? Well, this Technical Note will tell
you everything you need to know about what monitors are supported and how.

 Name  =  Segment Loader Limitations.cpt
 Path =  AMUG CD:Files:MacTechNotes:Operating System:Segment Loader Limitations.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Segment Loader Limitations - This Technical Note discusses the jump table
limitations of the Segment Loader and suggests some ways to work around
these limitations to minimize the problem.  These limitations are most
evident to developers using MacApp and other object-oriented environments.

 Name  =  Searching volumes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Searching volumes.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Searching volumes - This Technical Note discusses the PBCatSearch function
and tells why it should be used. It also provides simple algorithms for
searching both MFS and HFS volumes and discusses the problems with indexed
search routines. Changes since October 1988. Includes information on
PBCatSearch and notes the problems with indexed search routines. Source
code examples have been added and revised. Thanks to John Norstad at
Northwestern University for pointing out some of the shortcomings of the
indexed search routines. Thanks to the System 7 engineering team for adding
PBCatSearch.

 Name  =  Script Mgr Variables.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Script Mgr Variables.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 Script Mgr Variables - This Technical Note describes, in detail, the local
and global script variables.

 Name  =  Script Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Interapplication Comm.:Script Mgr Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Script Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Script Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Script Mgr Q&As.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Script Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Scrap Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Scrap Mgr Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Scrap Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Safe cdevs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Safe cdevs.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Safe cdevs - This Technical Note describes a potential problem with Control
Panel devices (cdevs) that contain EditText fields and presents a way to
avoid it.

 Name  =  SICNs in Menus.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:SICNs in Menus.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 SICNs in Menus - This Technical Note describes a new facility of the Menu
Manager which allows you to add reduced icons and small icons to your
menus. Changes since August 1989. Corrected references to SetItemCmd from
SetItmCmd.

 Name  =  SCSI Termination.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:SCSI Termination.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 SCSI Termination - This Technical Note discusses SCSI termination on the
Macintosh, including the new rules of termination which are necessary with
the advent of the high-speed Macintosh IIfx.

 Name  =  SCSI Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:SCSI Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 SCSI Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  SCSI H/W Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:SCSI H/W Q&As.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 SCSI H/W Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  SCSI Bugs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:SCSI Bugs.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 SCSI Bugs - There are a number of problems in the SCSI Manager; this note
lists the ones we know about, along with an explanation of what we’re doing
about them. Changes made for the 2/88 release are made to more accurately
reflect the state of the SCSI Manager. System 4.1 and 4.2 are very similar;
one bug was fixed in System 4.2.

 Name  =  SADE Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:SADE Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 SADE Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Resource in CDEV.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Resource in CDEV.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Resource in CDEV - This Technical Note discusses the new 'fwst' resource
added to some Control Panels under System 7.0 and later.

 Name  =  Resource Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Resource Mgr Q&As.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Resource Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Resource Manager Tips.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Resource Manager Tips.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Resource Manager Tips - This note discusses some problems with the Resource
Manager and how to work around them.

 Name  =  Reserved Resource Types.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Reserved Resource Types.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Reserved Resource Types - Your applications and desk accessories can create
their own resource types. To avoid using type names which have been or will
be used in the system, Apple has reserved all resource type names which
consist entirely of spaces ($20), lower-case letters ($61 through $7A), and
“international” characters (greater than $7F).

 Name  =  ResEdit Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:ResEdit Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 ResEdit Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  RTMP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:RTMP Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 RTMP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ROM Debugger.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:ROM Debugger.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ROM Debugger - The debugger in ROM (not present on the Macintosh 128,
Macintosh 512, or Macintosh XL) recognizes ROM commands in this document.

 Name  =  PurgeProc Note .cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:PurgeProc Note .cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 PurgeProc Note - This Technical Note discusses the use of the purgeProc
field of an application’s heap zone. Most applications will never need to
use a purgeProc. However, if your application requires the ability to
maintain purgeable handles containing data, or you need to have special
notification when a certain handle is purged, a purgeProc might help you.

 Name  =  pslt resource.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:pslt resource.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 pslt resource - One of the new resources that can be very helpful to some
NuBus™ developers is the 'pslt' resource. The only problem is that the
resource is not documented. This Technical Note takes care of the
documentation problem.

 Name  =  Projector Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Projector Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Projector Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Processor Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Processor Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Processor Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Process Overview Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:Process Overview Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Process Overview Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Process Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:Process Mgr Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Process Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Problem with GetVInfo.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Problem with GetVInfo.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Problem with GetVInfo - The high-level call GetVInfo (and its low-level
counterpart PBGetVInfo) may return inaccurate results for freeBytes when
running HFS. The high-level File Manager call GetVInfo returns the number
of free bytes on a volume as one of its parameters. Since GetVInfo is
really only glue that fills in a parameter block for you and then calls
PBGetVInfo, the values returned from it are subject to the limitations
(imposed for MFS) discussed in the File Manager chapter of Inside Macintosh
Volume IV.

 Name  =  Printing Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Printing Mgr Q&As.cpt
 Size: 18K         Date:10/29/92         Version:
 Description:
 Printing Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Printing Loop That Cares.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Printing Loop That Cares.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Printing Loop That Cares - This Technical Note discusses opening and
closing the Printing Manager with calls to _PrOpen and _PrClose as well as
how to handle errors at print time. Changes since October 1989. Added the
section on error checking, incorporating the error code descriptions
formerly found in Technical Note #72, Optimizing For The LaserWriter—
Techniques and an updated version of the information formerly found in
Technical Note #118, How To Check and Handle Printing Errors.

 Name  =  Printer Driver Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Printer Driver Q&As.cpt
 Size: 20K         Date:10/29/92         Version:
 Description:
 Printer Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  PrintMonitor Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:PrintMonitor Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 PrintMonitor Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Print Dialogs (Bad formatti.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Print Dialogs (Bad formatti.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Print Dialogs - This technical note discusses how to add your own items to
the Printing Manager’s dialogs.When the Printing Manager was initially
designed, great care was taken to make the interface to the printer drivers
as generic as possible in order to allow applications to print without
being device-specific. There are times, however, when this type of
non-specific interface interferes with the flexibility of an application.
An application may require additional information before printing which is
not part of the general Printing Manager interface.

 Name  =  PrintAction.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:PrintAction.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 PrintAction - This technical note describes how Print Drivers can access
the Script Manager Print Action routine to print unconventional text, such
as Japanese or Arabic.

 Name  =  Principia Off-Screen.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Principia Off-Screen.cpt
 Size: 57K         Date:10/29/92         Version:
 Description:
 Principia Off-Screen - Using Color QuickDraw to draw off screen is a common
requirement of applications and other kinds of programs that run on the
Macintosh. This Note discusses what Color QuickDraw needs in a graphics
environment and how to create one for off-screen drawing. A brief
discussion of GWorlds, which are off-screen graphics environments that are
set up by the system, is given to help you decide whether to use them or
the do-it-yourself techniques described in this Note for setting up an
off-screen graphics environment.

 Name  =  PrGeneral Bug.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:PrGeneral Bug.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 PrGeneral Bug - This technical note documents a bug in the implementation
of the PrGeneral procedure in the LaserWriter driver version 4.0. The bug
has to do with the format of the information returned by the GetRslData
opcode. This technical note will also describe a workaround for the
problem.

 Name  =  PrGeneral.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:PrGeneral.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 PrGeneral - The Printing Manager architecture has been expanded to include
a new procedure called PrGeneral. The features described here are advanced,
special-purpose features, intended to solve specific problems for those
applications that need them. The calls to determine printer resolution
introduce a good deal of complexity into the application’s code, and should
be used only when necessary.

 Name  =  Power Supply Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Power Supply Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Power Supply Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Power Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Power Mgr Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Power Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  PowerBook Miscellanea.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:PowerBook Miscellanea.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 PowerBook Miscellanea - This Technical Note describes some nonintuitive
ramifications of working with a battery-powered computer.

 Name  =  PostScript Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:PostScript Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 PostScript Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Position ind PS.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Position ind PS.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Position ind PS - This technical note describes a method for inserting
position-independent PostScript into QuickDraw pictures. There is a problem
with pictures that contain PostScript code. Sometimes the PostScript code
that is inserted into the picture is dependent on the position of the
picture on the page. The problem arises when these pictures are cut or
copied from their original position, and pasted into another position or
even into another document. The PostScript code will not know the new
location of the picture, and will not execute correctly.

 Name  =  Portable ROM Expansion.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Portable ROM Expansion.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Portable ROM Expansion - This Technical Note explains the practice of and
theory behind compatible use of the expansion ROM in the Macintosh
Portable. Due to the unique nature of the Macintosh Portable, developers
now have the ability to add ROM to the Macintosh. To provide for compatible
shared use of this ROM space with Apple and other developers, this Note
describes the feature and suggests methods of shared implementation.

 Name  =  Portable PDS Development.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Portable PDS Development.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Portable PDS Development - The Technical Note describes the unique aspects
of the Macintosh Portable Processor Direct Slot (PDS), including the severe
limitations in its use.

 Name  =  Popup MDEF Message 3.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Popup MDEF Message 3.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Popup MDEF Message 3 - In order to support popup menus, menu definition
procedures (MDEFs) must now respond to a new message, mPopupMsg. mPopupMsg
is message number 3. When your MDEF is called with this message, it should
calculate the rectangle in which the popup menu should appear.

 Name  =  PollProc.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:PollProc.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 PollProc - This Technical Note discusses how to make a PollProc for your
MIDI (Musical Instrument Digital Interface) driver on the Macintosh
PowerBook 140 and 170. For MIDI Consumption Only. You are writing your own
MIDI driver and your driver does not fully work on the PowerBook 170/140.
The PollProc support that might help solve your problem has been
undocumented until now because it has a bug in it which if ever fixed would
cause major problems with every PollProc ever made.

 Name  =  Plotting Small Icons.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Plotting Small Icons.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Plotting Small Icons - This Technical Note discusses the 'SICN' resource
format and how to plot one in a GrafPort. Changes since August 1989.
Corrected errors in the Pascal code and spruced up the rest.

 Name  =   Pixel2char.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text: Pixel2char.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
  Pixel2char - This Technical Note discusses the Pixel2Char routine provided
by the Script Manager. Changes since June 1989. Clarified information,
corrected minor errors, and replaced the illustration.

 Name  =  Pinouts.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Pinouts.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Pinouts - This note gives pinouts for Macintosh ports, cables, and other
products.

 Name  =  Pictures and Print.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Pictures and Print.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Pictures and Print - This technical note described some problems and
features of using Quickdraw pictures with the Printing Manager.  In
general, if your application prints Quickdraw pictures, you should read
this note.

 Name  =  Pictures and Clip Regions.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Pictures and Clip Regions.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Pictures and Clip Regions - This note describes a problem that affects
creation of QuickDraw pictures. When a GrafPort is created, the fields in
the GrafPort are given default values; one of these is the clip region,
which is set to the rectangle (–32767, –32767, 32767, 32767). If you create
a picture, then call DrawPicture with a destination rectangle that is not
the same size as the picFrame without ever changing the default clip
region, nothing will be drawn.

 Name  =  Picture Utility Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Picture Utility Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Picture Utility Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Picture Opcodes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Picture Opcodes.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Picture Opcodes - This technical note describes the internal format of the
QuickDraw picture data structure. This revision corrects some errors in the
opcode descriptions and provides some examples.

 Name  =  Picture Comments.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Picture Comments.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Picture Comments - Application-specific picture comment conflict and
registration is addressed, along with Developer Technical Support’s method
for solving it.

 Name  =  PictComments Real Deal.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:PictComments Real Deal.cpt
 Size: 37K         Date:10/29/92         Version:
 Description:
 PictComments Real Deal - Changes since March 1988:  This Note (formerly
titled “Optimizing for the LaserWriter—PicComments”) describes the picture
comments defined and interpreted by the Apple printer drivers. Most of the
picture comments are specific to PostScript, but we renamed the Note to
emphasize that LaserWriter printers are not necessarily PostScript devices,
and that QuickDraw printer drivers may implement their own picture comment
handling. This Note has been completely rewritten and incorporates all
additional insights gained during the last few years.

 Name  =  Performance Tuning.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Performance Tuning.cpt
 Size: 20K         Date:10/29/92         Version:
 Description:
 Performance Tuning - This Technical Note is a collection of useful ideas
and suggestions to help you decrease the time required to compile and link
under MPW. Some of the issues are even relevant to any development tools
running under the Macintosh environment. The Tech Note will also clarify
what performance tunings work, and which are marginal or may not work at
all.

 Name  =  Pascal to C PROC Parms.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Pascal to C PROC Parms.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Pascal to C PROC Parms - This Technical Note talks about nested procedures
and PROCEDURE parameters in Pascal and what to do when converting them into
C or C++. Changes since February 1990. Fixed some type coercion problems.

 Name  =  Pascal RoutiP.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Pascal RoutiP.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Pascal RoutiP - Routines passed by pointer are used in many places in
conjunction with Macintosh system routines. For example, filter procedures
for modal dialogs are passed by pointer, as are controls’ action procedures
(when calling TrackControl), and I/O completion routines.

 Name  =  Palette Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Palette Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Palette Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Palette Manager Changes 6.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Palette Manager Changes 6.0.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Palette Manager Changes 6.0 - This Technical Note describes the changes and
enhancements to the Palette Manager in System Software 6.0.2 and future
versions.

 Name  =  PackBits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:PackBits.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 PackBits - This Technical Note describes the format of data packed by the
Toolbox utility _PackBits and documents a change to the srcBytes limit and
possible worst case. Although you can simply unpack this data using
_UnPackBits, Apple provides this information for the terminally curious and
for those manipulating MacPaint® documents or PICT files by hand. Warning:
This format information is subject to change. Changes since November 1990.
A warning has been added about the handling of a flag-counter byte value of
-128.

 Name  =  PPC Toolbox Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Interapplication Comm.:PPC Toolbox Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 PPC Toolbox Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  PIdle Procedure .cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:PIdle Procedure .cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 PIdle Procedure - This Technical Note discusses how to defensively program
a pIdle procedure to work with the majority of print drivers in existence
today, and how to install it at print time.

 Name  =  PDS Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:PDS Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 PDS Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  PBShare & PBUnshare.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:PBShare & PBUnshare.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 PBShare & PBUnshare - This Technical Note documents three new File Manager
routines available on shared local volumes. The Pascal glue code, C glue
code, and the assembler equates and macros for the calls are included in
this note. Changes since October 1991. Corrected ioObjType input values for
PBGetUGEntry.

 Name  =  PBHSetVol.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:PBHSetVol.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 PBHSetVol - This note explains PBHSetVol, and why its use is not
recommended. PBHSetVol, like SetVol and PBSetVol, allows you to set the
current default volume and directory to be used with subsequent File
Manager calls. Unlike SetVol and PBSetVol, though, PBHSetVol lets you
specify the volume and the directory separately, using the ioVRefNum and
ioWDDirID fields.

 Name  =  PBGetCatInfo&ioFDirIndex.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:PBGetCatInfo&ioFDirIndex.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 PBGetCatInfo&ioFDirIndex - This technical note describes how to set
ioFDirIndex for PBGetCatInfo. The File Manager chapter of Inside Macintosh
volume IV is not very specific in describing how to use ioFDirIndex when
calling PBGetCatInfo. It correctly says that ioFDirIndex should be positive
if you are making indexed calls to PBGetCatInfo (analogous to making
indexed calls to PBGetVInfo as described in Technical Note #24).

 Name  =  PBClose the Barn Door.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:PBClose the Barn Door.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 PBClose the Barn Door - This Technical Note discusses the need for
Macintosh device drivers to implement _PBClose. You may get the idea when
implementing device drivers that _PBClose is superfluous.  After all, if
you have a resident driver for a NuBus™ video board, the only time your
driver is not needed is if the operating system is going away.  It might
seem that nothing important can happen after the operating system goes
away, so why bother with _PBClose?  Well, it turns out a lot can happen,
and this Note tells you why it is important to implement a Close (_PBClose)
routine.

 Name  =  PAP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:PAP Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 PAP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Owned Resource Shortcuts.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Owned Resource Shortcuts.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Owned Resource Shortcuts - To allow the Font/DA Mover to renumber desk
accessories as needed when moving them between system files, desk
accessories should use the “owned resource” protocol described in the
Resource Manager chapter of Inside Macintosh Volume I.

 Name  =  Our Checksum Bounced.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Our Checksum Bounced.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Our Checksum Bounced - This Technical Note discusses a fix to a SCSI
Manager bug which concerns all developers working with SCSI and NuBus™
device drivers.

 Name  =  Opening Serial Driver.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Opening Serial Driver.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Opening Serial Driver - This Technical Note describes the recommended,
safe, and compatible way to open the Macintosh serial driver, and it
explains why you should no longer check for port availability. Changes
since October 1989. Corrected syntax errors in the sample code.

 Name  =  Opening AppleTalk.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Opening AppleTalk.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Opening AppleTalk - This Technical Note describes the most effective, safe,
and compatible way to open the AppleTalk drivers, .MPP and .ATP. The
process of opening the AppleTalk drivers, .MPP and .ATP, can be greatly
simplified.  The AppleTalk Manager chapters of Inside Macintosh describe
the calls MPPOpen and ATPLoad for use by high-level languages.  They also
describe the process of examining low-memory globals SPConfig and PortBUse
before calling _Open for assembly language use of AppleTalk.

 Name  =  OpenRFPerm.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:OpenRFPerm.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 OpenRFPerm - This note corrects an error in the description of the Resource
Manager routine OpenRFPerm found in Inside Macintosh Volume IV.

 Name  =  OmegaSANE.cpt
 Path =  AMUG CD:Files:MacTechNotes:Operating System:OmegaSANE.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 OmegaSANE - System 7.0.1 introduced a new version of SANE (the Standard
Apple Numerics Environment) known as OmegaSANE.  This Note discusses the
features of OmegaSANE and the associated compatibility risks.

 Name  =  Old Style Colors.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Old Style Colors.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Old Style Colors - This Technical Note covers limitations of the original
Macintosh color model (eight-color) which Inside Macintosh, Volume I-173,
QuickDraw does not document. Changes since October 1989. Added definitions
of the old-style constants.

 Name  =  Off-Screen Bitmaps.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Off-Screen Bitmaps.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Off-Screen Bitmaps - This Technical Note provides an example of creating an
off-screen bitmap, drawing to it, and then copying from it to the screen.
Changes since April 1990. Clarified the section on window updates with
off-screen bitmaps to explicitly limit these updates to your own windows.

 Name  =  Object Pascal.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Object Pascal.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Object Pascal - Object Pascal must have a CODE segment named %_MethTables
in order to access object methods. In MacApp this is taken care of “behind
the scenes” so you don’t have to worry about it . However, if you are doing
a straight Object Pascal program, you must make sure that %_MethTables is
around when you need it. If it’s unloaded when you call a method, your
Macintosh will begin executing wild noncode and die a gruesome and horrible
death.

 Name  =  Number of Resources.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Number of Resources.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Number of Resources - This note describes the limitation of the number of
resources in a single resource file.

 Name  =  Nulls in Filenames.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Nulls in Filenames.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Nulls in Filenames - Some applications (loosely speaking so as to include
Desk Accessories, INITs, and what-have-you) generate or rename special
files on the fly so that they are not explicitly named by the user via
SFPutFile. Since the Macintosh file system is very liberal about filenames
and only excludes colons from the list of acceptable characters, this can
lead to some difficulties, both for the end user and for writers of other
programs which may see these files.

 Name  =  NuBus Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:NuBus Q&As.cpt
 Size: 18K         Date:10/29/92         Version:
 Description:
 NuBus Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  NuBus Power Limits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:NuBus Power Limits.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 NuBus Power Limits - This Technical Note discusses a very real power limit
for NuBus™ expansion cards and warns developers to heed this limit lest
they want users trashing their machines by overextending the Macintosh
power supply.

 Name  =  NuBus Physical Designs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:NuBus Physical Designs.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 NuBus Physical Designs - This Technical Note discusses the possible
problems you might run into while designing a NuBus™ card. It covers some
of the specifications which, if not followed, will have problems with
current Macintosh machines, and possibly future machines. Changes since
June 1989. Added warnings about the no component area and full-size NuBus
cards.

 Name  =  NuBus Interrupt Latency.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:NuBus Interrupt Latency.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 NuBus Interrupt Latency - This Technical Note discusses NuBus™ interrupt
latency, and why, contrary to popular belief, the Macintosh is not a
real-time machine. Changes since December 1988. Changed sample code to
defer cursor rendering to a deferred task rather than a “pseudo-VBL” task.
The Macintosh is not a real-time machine.  The Macintosh does not support
DMA. There are many variables in the Macintosh that make it impossible to
deterministically figure out exactly when things are going to happen.
Despite these facts, there are those who must push the envelope. For these
courageous adventurers, we provide the following information in the hope
that it speeds your journey.

 Name  =  NuBus Block Transfers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:NuBus Block Transfers.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 NuBus Block Transfers - This Technical Note describes the sResource entries
needed in a declaration ROM to inform NuBus™ masters when a board is
capable of receiving or sending block transfers. In addition to normal long
word transfers, the NuBus specification defines a number of block transfer
transactions. In block mode transfers, the system arbitrates for the bus a
single time and then performs a group of consecutive long word transfers
before releasing the bus. The reduction in bus arbitration time can result
in considerable gains in performance.

 Name  =  Notification Manager.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Notification Manager.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Notification Manager - This Technical Note describes the Notification
Manager, the part of the operating system that lets an application, desk
accessory, or driver alert the user. Changes since October 1989. Clarified
the section on error handling for calls to _NMInstall.

 Name  =  Notification Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:Notification Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Notification Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  New Resource Manager Calls.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:New Resource Manager Calls.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 New Resource Manager Calls - This Technical Note describes two new Resource
Manager calls that make opening and creating resource files much easier.

 Name  =  New CDEV Messages.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:New CDEV Messages.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 New CDEV Messages - This Technical Note describes some previously
undocumented messages that the Control Panel can send to a Control Panel
device (cdev).

 Name  =  NBP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:NBP Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 NBP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  My Life as a Pascal Object.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:My Life as a Pascal Object.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 My Life as a Pascal Object - This Technical Note discusses the PascalObject
base class, used, for instance, with MacApp programming. The Technical Note
describes how to write PascalObject derived classes that work with both
Object Pascal and C++ code linking. It also describes the current
restrictions and bugs with writing C++ code using PascalObject as the base
class. This Technical Note is based on MacApp 2.0(.1), MPW 3.2 and MPW C++
3.1.

 Name  =  Multiple Inheritance.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Multiple Inheritance.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Multiple Inheritance - This Technical Note answers a common question about
MPW C++:  “Why doesn’t HandleObject support multiple inheritance?”  It does
this by giving a brief overview of how multiple inheritance is implemented
in MPW C++.

 Name  =  Multidisk Installer.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Multidisk Installer.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Multidisk Installer - This Technical Note documents Apple’s Multidisk
Installer, and it is in addition to separate Installer documentation which
provides the details of writing scripts. Changes since September 1991.
Revised information on the use of Installer version 3.1 to version 3.2.
Revised information on the use of ScriptCheck version 3.2.1 with Installer
version 3.2. Added Common Questions and Answers relating to the use of the
Installer.

 Name  =  MultiFinder and _SetGrowZon.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:MultiFinder and _SetGrowZon.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MultiFinder and _SetGrowZon - MultiFinder patches the _SetGrowZone trap,
and this patch can cause your program to crash if you attempt to save and
restore the grow zone procedure.

 Name  =  MultiFinder Revisited.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:MultiFinder Revisited.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 MultiFinder Revisited - This Technical Note describes several new features
found in MultiFinder 6.0 and answers a few more commonly-asked questions.
Changes since December 1989. Added a warning to the section on
childDiedEvents about distribution of MultiFinder 6.1bx.

 Name  =  MultiFinder Questions.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:MultiFinder Questions.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 MultiFinder Questions - This technical note provides answers to some of the
more frequently asked questions about MultiFinder. The development name for
MultiFinder was Juggler, so the term “juggle” is used in this technical
note to denote a context switch.

 Name  =  MultiFinder Miscellanea.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:MultiFinder Miscellanea.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 MultiFinder Miscellanea - This Technical Note discusses MultiFinder issues
of which programmers should be aware. Changes since June 1988. Updated and
generalized sample code to reflect new MPW 3.0 calls in both C and Pascal
for saving and restoring A5 for interrupt code that accesses application
globals.  Removed text that can be found in Programmer’s Guide to
MultiFinder, and added a note about _PostEvent.

 Name  =  Moving Your Cat.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Moving Your Cat.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Moving Your Cat - This Technical Note clarifies the documentation in Inside
Macintosh for _PBCatMove and provides a demonstration on how to use it.
Changes since February 1989, Added a discussion of using NIL for the
destination name pointer, which is the simplest way to use _CatMove, and
revised the sample code to use the high-level File Manager calls. Thanks to
Tim Dierks of Apple Developer Technical Support U.K. for pointing out the
problems with the previous version of this Note.

 Name  =  Movie Toolbox Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:QuickTime:Movie Toolbox Q&As.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Movie Toolbox Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MoveHHi and SetResPurge.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:MoveHHi and SetResPurge.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 MoveHHi and SetResPurge - SetResPurge(TRUE) is called to make the Memory
Manager call the Resource Manager before purging a block specified by a
handle. If the handle is a handle to a resource, and its resChanged bit is
set, the resource data will be written out (using WriteResource). When
MoveHHi is called, even though the handle’s block is not actually being
purged, the resource data specified by the handle will be written out. An
application can prevent this by calling SetResPurge(FALSE) before calling
MoveHHi (and then calling SetResPurge(TRUE) after the MoveHHi call).

 Name  =  Movable Modal Dialogs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Movable Modal Dialogs.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Movable Modal Dialogs - This Technical Note describes the process by which
an application can remap the Help Manager 'hmnu' resource while a movable
modal dialog box is on the screen. The Help Manager handles the case for
modal dialog boxes but punts in the case of movable modal dialog boxes. The
following information will help you get the correct interface performance.

 Name  =  MoreMasters Revisited.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:MoreMasters Revisited.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 MoreMasters Revisited - MoreMasters should be called from CODE segment 1.
The number of master pointers that a program needs can be determined
empirically. MoreMasters can be tricked into creating the exact number of
master pointers desired.

 Name  =  Mixing HFS and C I/O.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Mixing HFS and C I/O.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Mixing HFS and C I/O - This Technical Note discusses the problem of mixing
calls to the Macintosh file system with calls to MPW C library file I/O
routines. Problems with Communication Between HFS and C. Frequently,
developers want to use both Macintosh file I/O and C file I/O.  Developers
who do this must keep in mind that they are combining two distinct file
representations (the Macintosh and ANSI C). The only limitation on mixing
HFS and C I/O functions is that they cannot be mixed on the same open file.
There are three reasons why this cannot be done.

 Name  =  Misc Tool Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Misc Tool Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Misc Tool Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Menu Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Menu Mgr Q&As.cpt
 Size: 25K         Date:10/29/92         Version:
 Description:
 Menu Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Memory Mgt Ov Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:Memory Mgt Ov Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Memory Mgt Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Memory Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:Memory Mgr Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Memory Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Memory H/W Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Memory H/W Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Memory H/W Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Managerial Abuse.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Managerial Abuse.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Managerial Abuse - When using the various pieces of the Macintosh operating
system there is a temptation to try to stretch the built-in Managers too
far. Developers should be aware of the intended purpose of the various
Managers and beware of using them for things that they were not designed to
handle. If extended beyond their design goals, they will become slow and
unwieldy.

 Name  =  MacsBug Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacsBug Q&As.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 MacsBug Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Macintosh SE/30.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Macintosh SE/30.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Macintosh SE/30 - This Technical Note discusses the Macintosh SE/30, items
of interest to developers, and sources for further information. Changes
since April 1989. Corrected an error in the addresses of the video display
buffers. The Macintosh SE/30 is a modification of the original Macintosh SE
concept. The SE/30 combines the modularity of the original SE with the
capabilities of the larger Macintosh IIx.  Although the name implies that
the SE/30 borrows many characteristics from the SE, there are actually
substantial differences between the two machines, and this Note addresses
some of those differences.

 Name  =  Macintosh Plus ROMs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Macintosh Plus ROMs.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Macintosh Plus ROMs - Readers Digest condensed version of Macintosh Plus
ROM history, or the truth according to Bo3bdar the everpresent.

 Name  =  MacinTalk Final Chapter.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacinTalk Final Chapter.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MacinTalk Final Chapter - This Technical Note discusses the MacinTalk
software product.

 Name  =  MacWorkstation Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:MacWorkstation Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 MacWorkstation Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MacTCP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:MacTCP Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 MacTCP Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Mac Plus Pinouts.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Mac Plus Pinouts.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Mac Plus Pinouts - This note gives pinout descriptions for some of the
Macintosh Plus ports and Macintosh Plus cables that are different than the
Macintosh 128K and 512K.

 Name  =  MacPaint Document Format.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacPaint Document Format.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 MacPaint Document Format - This Technical Note describes the internal
format of a MacPaint® document, which is a standard used by many other
programs.  This description is the same as that found in the “Macintosh
Miscellaneous” section of early Inside Macintosh versions. Changes since
October 1988. Fixed bugs in the example code.

 Name  =  Mac Mem Configurations.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Mac Mem Configurations.cpt
 Size:177K         Date:10/29/92         Version:
 Description:
 Mac Mem Configurations - This Technical Note describes the different
possible memory configurations of all models of the Macintosh family that
use Single In-line Memory Modules (SIMMs) as well as the non-SIMM memory
upgrade options of the Macintosh Portable and Macintosh Classic. (Special
thanks to Brian Howard for the Macintosh Plus and original SE drawings, and
for the inspiration for the other drawings.) This Note also describes the
obstacles to using four megabit (Mbit) DRAM SIMMs in Apple Macintosh
products to date.

 Name  =  Mac IIfx Inside Story.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Mac IIfx Inside Story.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Mac IIfx Inside Story - This Technical Note addresses various areas of
potential incompatibilities with the Macintosh IIfx and current software
applications and provides information about some of Apple’s compatibility
software updates.

 Name  =  Mac II Board Suppliers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Mac II Board Suppliers.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Mac II Board Suppliers - This note lists suppliers of parts that may be
helpful for Macintosh II board developers. If your company supplies these
parts, but is not listed here, please send a message to us (at the address
on Technical Note #0) and we’ll include you in the next revision of this
technical note.

 Name  =  Mac Common LISP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Mac Common LISP Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Mac Common LISP Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MacApp 'View' .cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacApp 'View' .cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 MacApp 'View' - This Technical Note describes the new MacApp 3.0 'View'
resource.

 Name  =  MacApp Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacApp Q&As.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 MacApp Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MacApp Bugs 3.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MacApp Bugs 3.0.cpt
 Size: 38K         Date:10/29/92         Version:
 Description:
 MacApp Bugs 3.0 - This Technical Note describes the latest information
about bugs or unexpected “features” in MacApp.  Where possible, solutions
and fixes are noted.  DTS intends this Note to be a complete list of all
known bugs in MacApp and will update it as old bugs are fixed or new ones
appear.  If you have encountered a bug or unexpected feature which is not
described here, be sure to let DTS know. Specific code examples and
suggested fixes are useful.

 Name  =  MPW for Non-Mac Systems.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW for Non-Mac Systems.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 MPW for Non-Mac Systems - This Technical Note discusses using MPW 3.0 for
creating software intended to run on 68000-based systems that do not
implement the Macintosh run-time architecture. These systems include NuBus™
cards, peripheral devices, and proprietary 68000 systems.

 Name  =  MPW Tool Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW Tool Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 MPW Tool Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  MPW Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 MPW Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MPW Pascal Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW Pascal Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 MPW Pascal Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW Library Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW Library Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPW Library Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW C Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW C Q&As.cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 MPW C Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  MPW C Functions.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW C Functions.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 MPW C Functions - Here’s the low-down on when C functions need not be
declared in include files.

 Name  =  MPW C++ Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW C++ Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 MPW C++ Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  MPW Assembly Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW Assembly Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPW Assembly Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  MPW 2.0.2 Bugs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW 2.0.2 Bugs.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 MPW 2.0.2 Bugs - This Technical Note describes latest information about
bugs or unexpected “features” in the MPW C, Pascal, and Assembler products
and the Toolbox and OS Interface Libraries.  We intend this Note to be a
complete list of all known bugs in these products, which will be updated as
old bugs are fixed, or new ones appear.  If you have encountered a bug or
unexpected feature which is not described here, be sure to let us know.
Specific code examples are useful.

 Name  =  MPW -mc68881.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW -mc68881.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 MPW -mc68881 - This Technical Note discusses MPW’s -mc68881 option, which
represents Extended values in 96 bits (instead of 80, as with software
SANE), and compatibility issues when using non-SANE system calls that
expect 80-bit Extended values. Changes since June 1990. Extended the
warning about explicitly checking for the presence of an FPU if an
application uses floating-point instructions to include the possibility of
FPU-less MC68040 products and also raised the issue of extended values
embedded in data structures.

 Name  =  MPW {$LOAD}.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:MPW {$LOAD}.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPW {$LOAD} - This technical note discusses the Pascal {$LOAD} directive as
well as how to unload the _DataInit and %_MethTables segments.

 Name  =  MPP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:MPP Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 MPP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Low-Level Printing.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Low-Level Printing.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Low-Level Printing - When you use the low-level printer driver to print,
you don’t get the benefits of the error checking that is done when you use
the high-level Printing Manager. So, if the user prints to an AppleTalk
ImageWriter (including an AppleTalk ImageWriter LQ) that is busy printing
another job, the driver doesn’t know whether the printer is busy, offline,
or disconnected.  Because of this, PrError will return (and PrintErr will
contain) abortErr.

 Name  =  Lock, Unlock the Range.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Lock, Unlock the Range.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Lock, Unlock the Range - This Technical Note discusses the _PBLockRange and
_PBUnlockRange routines; how they act on local and shared volumes and why
you should not set the ioPosMode field to fsFromLEOF in the parameter block
for those routines when accessing a file on an AppleShare volume. Changes
since April 1988. Added information on how _PBLockRange and _PBUnlockRange
really work.

 Name  =  Lo Down On Downloading.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Lo Down On Downloading.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Lo Down On Downloading - This technical note discusses a method for
downloading PostScript dictionaries automatically using the LaserWriter
driver.  It will also provide the format and use of the PREC(103) resource.
It will also describe some problems with the now obsolete PREC(201)
resource.  If you are using PostScript dictionaries, or either of these
resources, you should definitely read this note.

 Name  =  Little PowerBook Sleep.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Little PowerBook Sleep.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Little PowerBook Sleep - The purpose of this Note is to describe the
ramifications of resting, sleeping, and power-saving modes in the PowerBook
family of Macintosh computers, how they may affect your application, and
the appropriate ways to defeat them, when appropriate. It also describes
some nonintuitive ramifications of working with a battery-powered computer.

 Name  =  List Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:List Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 List Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  LaserWriter Util Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:LaserWriter Util Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 LaserWriter Util Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  LaserWriter ROM Bugs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:LaserWriter ROM Bugs.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 LaserWriter ROM Bugs - These are LaserWriter bugs that your users may
encounter when printing from any Macintosh application. These are for your
information; you cannot code around them. The bugs described here occur in
the 1.0 and 2.0 LaserWriter ROMs.

 Name  =  Laser Prep Routines.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Laser Prep Routines.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Laser Prep Routines - This technical note addresses the issues involved in
depending on the procedures and constants defined in the Laser Prep
dictionary. When you are writing an application that uses PostScript
heavily, it is very tempting to call the procedures already defined in the
Laser Prep dictionary, rather than taking up the space in the printer’s
memory with PostScript procedures of your own. Or, if a procedure in the
dictionary doesn’t do what you need it to do, it is tempting to go in and
change it to do what you really want.

 Name  =  Large Screen Displays.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Large Screen Displays.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Large Screen Displays - A number of third-party developers have announced
large-screen display peripherals for Macintosh. One of them, Radius Inc.,
has issued a set of guidelines for developers who wish to remain compatible
with their Radius FPD; unfortunately, one of their recommendations can
cause system crashes. This note suggests a more correct approach.

 Name  =  Large PICT Files.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Large PICT Files.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Large PICT Files - Now that we have scanners and other massive-picture
producing types of applications, there is a need to address the problem of
how to display a PICT format object that is bigger than a current PICT
resource is allowed to be. Note that this technique applies equally well to
version 1 and version 2 (word-opcode) pictures as produced by the Macintosh
II.

 Name  =  LW Optimization Techniques.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:LW Optimization Techniques.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 LW Optimization Techniques - This Technical Note discusses techniques for
optimizing code for printing on the LaserWriter. Changes since March 1988.
Updated the “Printable Paper Area” and “Memory Considerations” sections as
well as the printer IDs, moved the error messages from the end of the Note
to Technical Note #161, A Printing Loop That Cares…, and removed the
“Spool-A-Page/Print-A-Page” section because Technical Note #125, Effect of
Spool-A-Page/Print-A-Page on Shared Printers, already thoroughly covers
this topic.

 Name  =  LDEF Madness.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:LDEF Madness.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 LDEF Madness - This Technical Note uncovers a problem with writing Pascal
list definition procedures and two (yes, count  ’em, two) different methods
to work around it.

 Name  =  LAP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:LAP Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 LAP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  KillNBP.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:KillNBP.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 KillNBP - This technical note clears up some confusion regarding the Name
Binding Protocol KillNBP function. The description of the PKillNBP function
on page 519 of Inside Macintosh Volume V is somewhat confusing. The data
type of the parameter thePBptr is incorrectly given as ATPPBPtr and the
pointer to the queue element from the NBP call to be aborted is incorrectly
given as being passed in aKillQEl.

 Name  =  Keybd Resource Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Keybd Resource Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Keybd Resource Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Key Mapping.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Key Mapping.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Key Mapping - This Technical Note describes the Macintosh family key code
mapping scheme when running System file 4.1 and later. This Note also
provides a “safe” method for remapping keyboards. Changes since October
1990. Added a section on how 'KMAP' resources are matched to specific ADB
keyboard types and a section on the original Macintosh and Macintosh Plus
keyboards.

 Name  =  Joy of 32-Bit Clean.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Joy of 32-Bit Clean.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Joy of 32-Bit Clean - What to do (and what not to do) to make your programs
run under A/UX and future versions of the Macintosh System Software.
Changes since October 1988:  Added information on writing 32-bit clean
CDEFs, and updated A/UX information to reflect the capabilities of A/UX
1.1.

 Name  =  Is This a Spooler?.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Is This a Spooler?.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Is This a Spooler? - When the LaserShare spooler is on an AppleTalk
network, it acts like a LaserWriter-type device, which can be chosen and
communicated with much like a real LaserWriter. Some applications, however,
must communicate with a LaserWriter directly, not a spooler. If this is
true for your application, you can check whether you are actually talking
to a real LaserWriter by sending to the LaserWriter the following query.

 Name  =  ioPosOffset.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:ioPosOffset.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ioPosOffset - The Device Manager chapter of Inside Macintosh Volume II says
that ioPosOffset is passed to and returned by Read and Write calls. It also
says that “After the read [or write] is completed, the position is returned
in ioPosOffset…” Actually, ioPosOffset is not changed by either call. Also
note that device drivers should only look at the dCtlPosition field of the
DCE, and should not look directly at the ioPosOffset field of the parameter
block. The Device Manager sets up dCtlPosition for the driver, taking into
account both the ioPosMode and the ioPosOffset.

 Name  =  ioNamePtr.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:ioNamePtr.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ioNamePtr - It is very important to set ioNamePtr when making PB calls,
even if you don’t want  those calls to return a name. Whenever Inside
Macintosh indicates that ioNamePtr is either required for input or returns
something, you must set ioNamePtr to either nil (if you aren’t using a
name) or to point to storage for a Str255. If you don’t explicitly set
ioNamePtr, strange and unusual crashes may occur, depending on the
machine/configuration your code is run on.

 Name  =  ioCompletion.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:ioCompletion.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 ioCompletion - When making synchronous calls to the File Manager, it is not
necessary to clear ioCompletion field of the parameter block, since that is
done for you. Some earlier technotes explicitly cleared ioCompletion, with
the knowledge that this was unnecessary, to try to encourage developers to
fill in all fields of parameter blocks as indicated in Inside Macintosh.
By the way, this is true of all parameter calls—you only have to set fields
that are explicitly required.

 Name  =  Int'l Resource Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Int'l Resource Q&As.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Int'l Resource Q&A - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Internets.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Internets.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Internets - This Technical Note discusses how AppleTalk applications should
work across internets, groups of interconnected AppleTalk networks.  It
explains the differences between life on a single AppleTalk network and
life on an internet. Changes since March 1988. Removed the section on
AppleTalk retry timers, as it is no longer accurate.

 Name  =  International Canceling.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:International Canceling.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 International Canceling - This Technical Note describes potential problems
canceling operations with the Command-period key sequence and international
keyboards.

 Name  =  InternationalCha.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:InternationalCha.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 InternationalCha - The International Utilities package and the
international resources have been changed with System file 4.1 to take
advantage of the Script Manager.

 Name  =  Installer Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Installer Q&As.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Installer Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Inside Object Pascal.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Inside Object Pascal.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Inside Object Pascal - This Technical Note briefly explains why Object
Pascal and MacApp should only be used to write applications and MPW tools.
Although Pascal can be used to write desk accessories, drivers, XCMDs and
other types of stand–alone code, and Object Pascal is an extension of
Pascal, Object Pascal cannot be used to write anything other than an
application.  This limitation is due to the fact that Object Pascal method
dispatching relies on a valid A5 pointing to a jump table.  Because MacApp
is written in Object Pascal, this limitation applies to it as well.

 Name  =  Image Writer IIMotio.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Image Writer IIMotio.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Image Writer II Motion - The purpose of this technical note is to answer
the many questions asked about why the paper moves the way it does on the
ImageWriter II.

 Name  =  Image Compr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:QuickTime:Image Compr Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Image Compr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Identifying Features.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Identifying Features.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Identifying Features - This technical note explains how to check at run
time to see if specific functionality, such as the “new” TextEdit, is
present. Applications should strive to be compatible across all
Macintoshes, but there are times when an application must have knowledge
about the machine that it is running on.  The new trap, SysEnvirons, will
give an application most of the information that it requires (what
hardware, what version of system software…).

 Name  =  Icon Drawing in 7.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Icon Drawing in 7.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Icon Drawing in 7 - This Technical Note describes how to utilize the
built-in System 7 icon drawing utility. Use this information to better
conform to the System 7 visual human interface. Changes since May 1992. In
this Note, we replaced the C and Pascal interface files and corrected the
related text. So much text was tweaked that change bars are used only on
code changes.

 Name  =  ISO 9660 CD ROM Format.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:ISO 9660 CD ROM Format.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ISO 9660 CD ROM Format - What’s Wrong with my High Sierra Disc? Generally,
if a Macintosh has problems with a High Sierra disc, it’s because the disc
in question  doesn’t really conform to the High Sierra specification.

 Name  =  IOP Diffs Under A/UX.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:IOP Diffs Under A/UX.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 IOP Diffs Under A/UX - This Technical Note discusses use of the Macintosh
IIfx IOP-based serial driver under A/UX, especially under certain error
conditions which cause it to perform differently than documented in
termio(7).  (The SCC driver, used on non-IOP machines, conforms to
termio(7) in all cases.)  References to “the driver” herein refer to the
IOP-based serial driver, seriop.c.

 Name  =  HyperCard and You.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:HyperCard and You.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 HyperCard and You - This Technical Note describes some HyperCard anomalies
with which developers should be familiar when developing stackware, and it
documents differences between HyperCard versions where appropriate.
Changes since November 1987. Updated material with regard to HyperCard 2.0
and condensing or obsoleting information on bugs which have been addressed.

 Name  =  Help Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Help Mgr Q&As.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 Help Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Hard Disk Hacking.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Hard Disk Hacking.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Hard Disk Hacking - For those of a technical bent with some extra time, you
can build your own hard disk system from a cheap SCSI drive and a driver
that you write. This is not a project for those short on time, so beware.

 Name  =  Handles vs. Pointers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:Handles vs. Pointers.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Handles vs. Pointers - A handle is a handle and a pointer is a pointer.
Applications should avoid embedding non-relocatable objects (that the
system assumes will never move) in handles. In order to avoid
fragmentation, some applications embed pointers (non-relocatable memory
manager objects) in handles, so that the handles can be moved around as
needed. This can cause several problems, especially with the Macintosh II,
and should be avoided.

 Name  =  HFS Tidbits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:HFS Tidbits.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 HFS Tidbits - This Technical Note describes two poorly documented features
of the File Manager.

 Name  =  HFS Ruminations.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:HFS Ruminations.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 HFS Ruminations - This technical note contains some thoughts concerning
HFS.

 Name  =  HFS Elucidations.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:HFS Elucidations.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 HFS Elucidations - This technical note will describe a few problems that
can occur while using HFS. It will also describe ways to avoid these
problems.

 Name  =  HFS Comaptibility.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:HFS Comaptibility.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 HFS Comaptibility - This technical note tells you how to make sure that
your applications run under the Hierarchical File System (HFS). The
Hierarchical File System (HFS) provides fast, efficient management of
larger volumes than the original Macintosh File System (MFS). Since HFS is
hierarchical, HFS folders have a meaning different from MFS folders. In
MFS, a folder has only graphical significance—it is only used by the Finder
as a means of visually grouping files. The MFS directory structure is
actually flat (all files are at the ‘root’ level). Under HFS, a folder is a
directory that can contain files and other directories.

 Name  =  Globals from Asm.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Globals from Asm.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Globals from Asm - This technical note demonstrates how to access MPW
Pascal and MPW C globals from the MPW Assembler.

 Name  =  Gimmie Depth or Death.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Gimmie Depth or Death.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Gimmie Depth or Death - This Technical Note describes two new system calls
that allow an application to change the depth and flags for a given device
and also check whether a device supports a particular depth and flags
setting.  Apple provides these calls to give developers a better way to
help users make changes when they consider it appropriate.  Abusive use of
these calls is a sure way to guarantee that the Thought Police come after
you to confiscate your Macintoshes, your stock of Mountain Dew®, and your
Technical Notes binder.  This Note assumes familiarity with Inside
Macintosh, Volume V, Graphics Devices.

 Name  =  Getting thru CUSToms.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Getting thru CUSToms.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Getting thru CUSToms - This technical note provides a way for developers to
allow sophisticated users to add code to an off-the-shelf application.
Using this scheme, the user can easily install the code module; the
application has to know how to call it and, optionally, be able to respond
to a set of predefined calls from the custom package.

 Name  =  Getting a Full Pathname.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Getting a Full Pathname.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Getting a Full Pathname - This Technical Note describes how to generate a
full pathname, given either a Working Directory ID or a real vRefNum and a
DirID. By using the techniques shown in this Note, you can find the full
pathname from information such as that returned by Standard File. Changes
since June 89. Added a note on how to check for A/UX. Fixed bug in C
version:  BlockMove() parameters were reversed in pStrcpy(); added range
checking to pStrCat(); changed references from “longint” to “long”.  Fixed
bug in Pascal and C versions. Changed fsRtDir to fsRtdirID and made
references to gHaveAUX consistent.

 Name  =  GetPhysical .cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:GetPhysical .cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 GetPhysical - The purpose of this Note is twofold. First, it describes in
detail how to use the GetPhysical routine. This routine is critical to the
support of alternate bus masters on certain machines without Virtual Memory
(VM) and all machines with VM. Included is an ancillary discussion of
several closely-related VM routines. Second, it reiterates a number of
issues important to VM compatibility and elucidates some of the deeper VM
issues of which specialized developers should be aware. Compatibility
issues are especially important for developers of SCSI drivers, NuBus™
master hardware, and code which runs at interrupt time.

 Name  =  GetNextEvent & Blinking App.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:GetNextEvent & Blinking App.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 GetNextEvent & Blinking App - Wherein arcane mysteries are unraveled so you
can make the Alarm Clock (or a similar desk accessory) blink the Apple menu
at the appointed second. Also, why GetNextEvent is a good thing.

 Name  =  GetNewDialog Errors.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:GetNewDialog Errors.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 GetNewDialog Errors - When calling GetNewDialog to retrieve a dialog
template from a previously opened resource file, how are error conditions
indicated to the caller? Unfortunately, they aren’t. The Dialog Manager
calls GetResource and assumes the returned value is good. Since the Dialog
Manager doesn’t check, you have two choices. Your first choice is to call
GetResource for the dialog template, item list, and any resources needed by
items in the item list yourself. But what do you do when you find the
resources aren’t there?

 Name  =  _Gestalt & System Environs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:_Gestalt & System Environs.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 _Gestalt & System Environs - This Technical Note discusses the latest
changes and improvements to the _Gestalt and _SysEnvirons calls. Changes
since May 1992. Added information on the gestaltMachineType selector for
the Quadra 950, Macintosh LC II, Powerbook 145, and future system software.

 Name  =  GDevice Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:GDevice Mgr Q&As.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 GDevice Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Fun with PrJobMerge (#2).cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Fun with PrJobMerge (#2).cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Fun with PrJobMerge (#2) - This Technical Note discusses some interesting
behavior you’ll encounter while using PrJobMerge with the 7.0 and 7.1
versions of the LaserWriter driver. Changes since March 1992. Corrected the
Vulcan-like “THPring” typo to correctly read “THPrint,” and changed a
comment in the code to mean what I originally meant.

 Name  =  Forcing Floppy Size.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Forcing Floppy Size.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Forcing Floppy Size - This document explains how to initialize a disk as
either single- or double- sided. It only applies to 800K drives, of course.
You can call the disk driver to initialize a disk and determine
programmatically whether it should be initialized as single- (MFS) or
double- (HFS) sided. All you have to do is call the .Sony driver directly
to do the formatting then the Disk Initialization Package to write the
directory information.

 Name  =  Fonts and the Script Mgr.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Fonts and the Script Mgr.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Fonts and the Script Mgr - This Technical Note describes how the Script
Manager uses the font family ID to determine a script code.

 Name  =  Font Names.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Fonts:Font Names.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Font Names - This note recommends the use of font names rather than font
numbers. The Font Manager chapter of Inside Macintosh Volume IV claims that
font family numbers 0 through 127 are reserved for use by Apple, and
numbers 128 through 255 are assigned by Apple for fonts created by software
developers. This is no longer true. Developer Technical Support does not
assign font family numbers. You should only use font numbers to reference
the system font (font 0) and application default font (font 1). All other
fonts should be identified by name. The Font/DA Mover will renumber a font
when moving it into a file containing a conflicting font family.

 Name  =  Font Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Font Mgr Q&As.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Font Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Font Height Tables.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Font Height Tables.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Font Height Tables - This technical note describes how the Font Manager
(except in 64K ROMs) calculates height tables for fonts and how you can
force recalculation.

 Name  =  Font File Icons.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Fonts:Font File Icons.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Font File Icons - This Technical Note discusses why you should not link
directly from your font files to the font icons provided by LaserWriter
driver 5.2 and later. Changes since December 1988. Added some useful tips
and described the method required to bundle an icon to your font file.

 Name  =  Font Family Numbers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Fonts:Font Family Numbers.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Font Family Numbers - This Technical Note discusses the range of numbers
available for identifying font families, how they are allocated among
script systems, and what numbers should be used for fonts that were
designed to be used as a tool in an application. Changes since August 1990.
Apple Computer no longer registers font family ID numbers; this note has
been altered to reflect the change in policy. Also, the relationship of
outline fonts to font families is discussed briefly.

 Name  =  Font/DA Mover.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Font/DA Mover.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Font/DA Mover - This technical note describes how to make sure that your
desk accessory will work after being moved by Font/Desk Accessory Mover.

 Name  =  Fond of FONDs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Fond of FONDs.cpt
 Size: 21K         Date:10/29/92         Version:
 Description:
 Fond of FONDs - This Technical Note takes the place of Tech Note #26,
“Character vs. String Operations in QuickDraw” by Bryan Stearns (March
1988), which pointed out the possible differences between the results of a
StringWidth call and successive calls to CharWidth. This Note updates and
brings into a broader context the issues related to text measuring. It also
provides additional documentation on font family resources ('FOND's), and
addresses various other frequently asked questions related to the Font
Manager.

 Name  =  Floppy Disk Int Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Floppy Disk Int Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Floppy Disk Int Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Finding Drivers in.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Finding Drivers in.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Finding Drivers - This note will explain how code can be written to
determine the reference number of a previously installed driver when only
the name is known. Changes since 2/86, Since the driver can be purged and
the DCE still be allocated, the code now tests for dCtlDriver being NIL as
well.

 Name  =  Finders and Drives.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Finders and Drives.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Finders and Drives - This technical note describes the differences in the
way the 1.1g, 4.1, 5.0 and newer Finders communicate with foreign
(non-Sony) disk drives.

 Name  =  Finder Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Finder Q&As.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 Finder Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  Finder Notes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Finder Notes.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Finder Notes - The Finder has undergone a couple of changes you should keep
in mind when creating the “bundle” information for your application.

 Name  =  Finder Flags.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Finder Flags.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Finder Flags - This revision corrects the meanings of bits 6 and 7, which
were interchanged in the older version of this technical note. ResEdit uses
these bits incorrectly in versions older than 1.2.

 Name  =  FindDItem.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:FindDItem.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 FindDItem - FindDItem is a potentially useful call which returns the number
of a dialog item given a point in local coordinates and a dialog handle. It
returns an item number of –1 if no item’s rectangle overlaps the point.
This is all well and good, except you don’t get back quite what you would
expect.

 Name  =  File Sharing .cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:File Sharing .cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 File Sharing - This Note describes modifications to the existing File
Manager routines, PBGetCatInfo, PBHGetDirAccess, PBHSetDirAccess,
PBHSetFLock and PBHRstFLock, when used on volumes prepared by Macintosh
System 7 File Sharing. There are several differences between System 7 File
Sharing and AppleShare 2.0.1. This Note describes what those differences
mean when calling PBGetCatInfo, PBHGetDirAccess, PBHSetDirAccess,
PBHSetFLock and PBHRstFLock on local volumes that return bHasPersonal
AccessPrivileges to PBHGetVolParms.

 Name  =  File Mgt Overview Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:File Mgt Overview Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 File Mgt Overview Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  File Handling Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:File Handling Q&As.cpt
 Size: 24K         Date:10/29/92         Version:
 Description:
 File Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Feeder Fodder.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Feeder Fodder.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 Feeder Fodder - This Technical Note discusses the new Feeder button
available in the 6.1, and 7.0 versions of the LaserWriter driver.  This
Feeder button mechanism allows developers to insert code into the
LaserWriter driver to support a sheet feeder connected to a LaserWriter.
This Note provides a description of the button, as well as information
required to implement one.

 Name  =  Fear No SCSI.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Fear No SCSI.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Fear No SCSI - This Technical Note discusses the answers to questions that
are often asked about SCSI and that are not discussed in Inside Macintosh
Volumes IV and V.

 Name  =  FPU Operations on Quadras.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:FPU Operations on Quadras.cpt
 Size: 19K         Date:10/29/92         Version:
 Description:
 FPU Operations on Quadras - This Technical Note discusses floating-point
unit (FPU) instruction support on Macintosh Quadra platforms with special
emphasis given to compatibility and performance concerns. Changes since
June 1992. Added warning to check for an FPU before attempting to execute
FPU instructions.

 Name  =  Excellent CD Notes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Excellent CD Notes.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Excellent CD Notes - This Technical Note discusses issues concerning the
use of the AppleCD SC drive, the Apple CD-ROM device driver, and the
Foreign File Access software extension.

 Name  =  Event Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Event Mgr Q&As.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Event Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Ethernet Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Ethernet Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Ethernet Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Error in FCBPBRec.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Error in FCBPBRec.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Error in FCBPBRec - The declaration of a FCBPBRec is wrong in Inside
Macintosh Volume IV  and early versions of MPW. This has been fixed in MPW
1.0 and newer. An error was made in the declaration of an FCBPBRec
parameter block that is used in PBGetFCBInfo calls. The field ioFCBIndx was
incorrectly listed as a LONGINT.

 Name  =  Edition Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Interapplication Comm.:Edition Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Edition Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Edit File Format.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Edit File Format.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Edit File Format - This technical note describes the format of the files
created by Edit. It has been verified for versions 1.x and 2.0.

 Name  =  Drivers and DAs in.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Drivers and DAs in.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Drivers and DAs - This Technical Note describes a few complications which
rear their rather ugly little heads when a desk accessory or driver needs
periodic time.  It also presents a few solutions to work around these
problems and make life easier, at least periodically. Changes since August
1989, Corrected _BitClr and _BitSet examples.  Okay, I admit it.  I was
having too good of a time when I wrote the original Note and messed up the
bit manipulations at the end.  My vision was blurred; I was in no condition
to see those tiny little things.

 Name  =  Drive Queue Elemets.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Drive Queue Elemets.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Drive Queue Elemets - This note expands on Inside Macintosh’s definition of
the drive queue, which is given in the File Manager chapter.

 Name  =  Drawing TextGraf.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Drawing TextGraf.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Drawing TextGraf - When you draw a character into a GrafPort, your program
will die with an address error if the width of the GrafPort is smaller than
the width of the character. If you check before drawing the character to
see if the GrafPort is wide enough, you can avoid this unfortunate tragedy.

 Name  =  Drawing Icons.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Drawing Icons.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Drawing Icons - Using resources of type ICON allows drawing of icons in
srcOr mode.  Using resources of type ICN# allows for more variety when
drawing icons.

 Name  =  Dont Use ResApp Byt.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Dont Use ResApp Byt.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Dont Use ResApp Byt - The section of the Resource Manager chapter of Inside
Macintosh which describes the internal format of a resource file shows an
area of the resource header labeled “available for application data.” You
should not use this area—it is used by the Resource Manager.

 Name  =  Don’t Call ADBReInit in sys.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Don’t Call ADBReInit in sys.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Don’t Call ADBReInit in sys - Because of a bug (which causes auto-repeat)
in the ROM version of the Macintosh SE keyboard driver, a patch was placed
in System 4.1. If ADBReInit is called, the ROM version of the keyboard
driver will be reloaded, and the RAM version of the driver with the patches
will not be used. Therefore, it is recommended that ADBReInit not be called
on the Macintosh SE until the problem is fixed. (There is no need to call
ADBReInit.) This problem will not occur with the Macintosh II ROM version
of the keyboard driver.

 Name  =  Document Names.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Document Names.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Document Names - Our compatibility testing for LaserShare (Apple’s
LaserWriter spooler) has turned up a number of applications that do not
provide the Printing Manager with a document name; although this feature is
not required, it is nice for users that share printers.

 Name  =  Disk Driver Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Disk Driver Q&As.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Disk Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Directory Handling Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Directory Handling Q&As.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 Directory Handling Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Dialog Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Dialog Mgr Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Dialog Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  DiaglogsfromDAs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:DiaglogsfromDAs.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 DiaglogsfromDAs - When a desk accessory creates a window (including a
modeless dialog window) it must set the windowKind to its refnum—a negative
number. When the application calls GetNextEvent, the Event Manager calls
SystemEvent, which checks to see if the event belongs to a desk accessory.
SystemEvent checks the windowKind of the frontmost window, and uses the
(negative) number for the refnum to make a control call, giving the desk
accessory a shot at the event. Then SystemEvent returns TRUE, and
GetNextEvent returns FALSE.

 Name  =  Device Mgt Ov Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Device Mgt Ov Q&As.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Device Mgt Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Device Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Device Mgr Q&As.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Device Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Device Independen Printing.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Device Independen Printing.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Device Independen Printing - The Printing Manager was designed to give
Macintosh applications a device- independent method of printing, but we
have provided device-dependent information, such as the contents of the
print record. Due to the large number of printer-type drivers becoming
available (even for non-printer devices) device independence is more
necessary than ever. What this means to you, as a developer, is that we
will no longer be providing (or supporting) information regarding the
internal structure of the print record.

 Name  =  Device Driver Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Device Driver Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Device Driver Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Desktop Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Desktop Mgr Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Desktop Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Desktop File Resources.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Desktop File Resources.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Desktop File Resources - This Technical Note describes the resources found
in the Desktop file.  You should not base anything critical on the format
of the Desktop file. System 7 already uses another scheme as did AppleShare
2.0 under System 6.0.x.

 Name  =  Desktop File Limits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Desktop File Limits.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Desktop File Limits - There is a limit to the number of applications/files
that the Finder can “see” on a single volume. This limitation is imposed by
the Desktop file. The Desktop file is a resource file that the Finder uses
to keep track of information about files and applications, including Finder
file comments (Get Info comments), and how these files and applications
relate to each other.

 Name  =  DeskHook and INIT Evils.cpt
 Path =  AMUG CD:Files:MacTechNotes:Operating System:DeskHook and INIT Evils.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 DeskHook and INIT Evils - This Technical Note discusses INIT evils, the
foremost of which deals with clearing DeskHook and DragHook at INIT time.
Changes since August 1989. Added warning about clearing DragHook.

 Name  =  Deferred Task Traps.cpt
 Path =  AMUG CD:Files:MacTechNotes:Processes:Deferred Task Traps.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Deferred Task Traps - This Technical Note shows how to determine when the
Deferred Task Manager is available, points out a compatibility issue with
the Macintosh Plus, explains how and when deferred tasks are called, and
shows how to access the dtParm parameter from deferred tasks written in C
and Pascal.

 Name  =  Debug with Purge.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Debug with Purge.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Debug with Purge  - If you are having problems finding bugs like handles
that aren’t locked down when they should be, or resources that aren’t there
when they’re supposed to be, there is a handy technique for forcing these
problems to the surface.

 Name  =  Debugging Tips.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Debugging Tips.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Debugging Tips - This presents a few tips which may make your debugging
easier.

 Name  =  Date & Time Problems.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Date & Time Problems.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Date & Time Problems - This Technical Note describes known bugs and
features in and solutions to the date and time routines introduced in
Script Manager 2.0.

 Name  =  Data In Resource Fork.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Data In Resource Fork.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Data In Resource Fork - Don’t use the resource fork of a file for
non-resource data. Parts of the system (including the File Manager and the
Finder) assume that if this fork exists, it will contain valid Resource
Manager information. PBOpenRF was provided to allow copying of the resource
fork of a file in its entirety, without Resource Manager interpretation. Do
not use it to open “another data fork.”

 Name  =  DDP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:DDP Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 DDP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  DAM Extensions.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:DAM Extensions.cpt
 Size: 14K         Date:10/29/92         Version:
 Description:
 DAM Extensions - This Technical Note discusses coding data access
extensions that provide an interface between the Data Access Manager and
remote data sources. Each of the functions that a data access extension
must implement is described.

 Name  =  Custom Menu Flashing Bug.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Custom Menu Flashing Bug.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Custom Menu Flashing Bug - Selected menu items in a custom 'MDEF' resource
do not flash correctly due to a bug in the Menu Manager.  This Technical
Note describes the problem and explains how to make your 'MDEF' flash
correctly.

 Name  =  Creating In Drop Folders.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Creating In Drop Folders.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Creating In Drop Folders - This technical note outlines the steps an
application must take to create files inside AppleShare drop folders.
The AppleShare File Server allows the creation of drop folders. These are
folders for which the user has the Make Changes privilege (write access),
but not See Files (read access) or See Folders (search access).

 Name  =  CreateResFile & PMSP.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:CreateResFile & PMSP.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 CreateResFile & PMSP - CreateResFile checks to see if a resource file with
a given name exists, and if it does, returns a dupFNErr (–48) error.
Unfortunately, to do this check, CreateResFile uses a call that follows the
Poor Man’s Search Path (PMSP).

 Name  =  CopyBits & GC QuickDraw.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:CopyBits & GC QuickDraw.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 CopyBits & GC QuickDraw - This Technical Note discusses conditions that may
cause _CopyBits to slow down when QuickDraw acceleration is on via the
Apple 8•24 GC Display Card.

 Name  =  Coop with Coprocessor.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Coop with Coprocessor.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Coop with Coprocessor - The use of the 68881 or 68882 coprocessor is
usually handled by the SANE package or by a development system’s libraries.
Some developers may wish to use the coprocessor during special
circumstances, such as at interrupt level or installing their own hardware
floating point exception handlers. In these two situations, there are
special requirements that must be met. These requirements will require
floating–point assembly code and are discussed in this Technical Note.

 Name  =  Control Panel Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Control Panel Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Control Panel Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Control Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Control Mgr Q&As.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Control Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Control & Status Calls.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Control & Status Calls.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Control & Status Calls - This Technical Note discusses situations under
which high-level Status calls do not work correctly and PBStatus calls
should be made instead. Changes since February 1990, Information has been
added describing similar problems with high-level Control calls.

 Name  =  Connection Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Communications:Connection Mgr Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Connection Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Compleat TeachText.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Compleat TeachText.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 Compleat TeachText - This Technical Note explains how to use TeachText to
create release notes, complete with pictures, which every Macintosh owner
can read.  This Note assumes familiarity with ResEdit.

 Name  =  Compatibility Why and How.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Compatibility Why and How.cpt
 Size: 30K         Date:10/29/92         Version:
 Description:
 Compatibility Why and How - While creating or revising any program for the
Macintosh, you should be aware of the most common reasons why programs fail
on various versions of the Macintosh. This note will detail some common
failure modes, why they occur, and how to avoid them.

 Name  =  Compatability Guidelines.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Compatability Guidelines.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Compatability Guidelines - Apple has many enhancements planned for the
Macintosh family of computers. To help ensure your software’s compatibility
with these enhancements, check each item in this note to be sure that
you’re following the recommendations.

 Name  =  Command-Shift Keys.cpt
 Path =  AMUG CD:Files:MacTechNotes:Operating System:Command-Shift Keys.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Command-Shift Keys - In the standard system, there are two Command-Shift-
number key combinations that are automatically captured and processed by
GetNextEvent.

 Name  =  Comm Toolbox Ov Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Communications:Comm Toolbox Ov Q&As.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Comm Toolbox Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Colorizing CopyBits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Colorizing CopyBits.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Colorizing CopyBits - Inside Macintosh Volume V states that the foreground
and background colors are applied to an image during a CopyBits or CopyMask
call. Accidental use of this feature can create bizarre coloring effects.
This note explains what happens, how to avoid problems, and how to use it.

 Name  =  Color, Windows & 7.0.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Color, Windows & 7.0.cpt
 Size: 20K         Date:10/29/92         Version:
 Description:
 Color, Windows & 7.0 - System software version 7.0 introduces a new look
for the Macintosh desktop. In order to implement those changes, 'wctb' and
'cctb' resources have changed in both form and use; it is now up to
developers to take the lead and help the new standard work. The task can be
divided into two main areas: in most cases all developers have to do is to
stick to the system resources in order to provide a homogeneous feel to the
user; developers in this group need only make sure the old 'wctb's are
disposed of and that all dialogs and windows are based on CGrafPorts.

 Name  =  Color QuickDraw Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Color QuickDraw Q&As.cpt
 Size: 36K         Date:10/29/92         Version:
 Description:
 Color QuickDraw Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Color Printing.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Printing:Color Printing.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 Color Printing - This discusses color printing in a Macintosh application.
Whereas the original eight-color model of QuickDraw was sufficient for
printing in color on the ImageWriter II, the introduction of Color
QuickDraw has created the need for more sophisticated printing methods.

 Name  =  Color Monitor Connection.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Color Monitor Connection.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Color Monitor Connection - This Technical Note describes how to connect the
Macintosh II Video Card, Macintosh IIci built-in video, and Macintosh LC
video to third-party monitors. Changes since February 1990. Added pinout
description for the Macintosh LC external video connector and a Macintosh
LC to VGA monitor adapter cable.  Standardized signal names throughout
Note.

 Name  =  Color Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Color Mgr Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Color Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Color Cursor Cursing.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Color Cursor Cursing.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Color Cursor Cursing - Working with color cursors you create from scratch
can cause headaches. This Technical Note may help a bit. Changes since June
1989. Added a warning about purgeable 'clut' resources.

 Name  =  Clickless Sound.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Clickless Sound.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Clickless Sound - This Technical Note formerly described how to use the
Sound Driver to produce continuous sound without clicking. Changes since
March 1988. The continuous sound technique is no longer recommended.

 Name  =  'ckid' Resource Format.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:'ckid' Resource Format.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 'ckid' Resource Format - This Technical Note describes the 'ckid' resource
format used by MPW’s Projector.  If you are writing an editor or
development system, you may wish to allow or disallow file modification
based on the information in the resource.

 Name  =  Chooser PACK.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:Chooser PACK.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Chooser PACK - Beginning with version 3.2, the Chooser has been enhanced to
provide support for additional controls.

 Name  =  ChangedResource.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:ChangedResource.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ChangedResource - The toolbox trap ChangedResource is used to inform the
Resource Manager that the contents of a resource have changed and should be
written to disk. The actual write occurs on the next call to WriteResource
(for the specific resource) or UpdateResFile (for the resource file
containing the specified resource). When called, ChangedResource reserves
enough disk space to contain the changed resource. A little-known “feature”
of ChangedResource is that it reserves disk space every time it is called.

 Name  =  Category Index.cpt
 Path =  AMUG CD:Files:MacTechNotes: Indexes:Category Index.cpt
 Size: 41K         Date:10/29/92         Version:
 Description:
 Category Index - This index lists each Technical Note by Cataogry, and
gives a brief description of of it's contents.

 Name  =  Calling SetResLoad.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Calling SetResLoad.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 Calling SetResLoad - Calling SetResLoad(FALSE) can be useful if you need to
get a handle to a resource, without causing the resource to be loaded from
disk if it isn’t already in memory. SetResLoad changes the value of the
low-memory global ResLoad (at location $A5E).

 Name  =  Caching.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Caching.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 Caching - This technical note describes disk and File System caching on the
Macintosh, with particular emphasis on the high-level File System cache. Of
the three caches used for file I/O, this is the one which could have the
most impact on your program.

 Name  =  Cache As Cache Can.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Cache As Cache Can.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 Cache As Cache Can - This Technical Note documents cache behavior,
manipulation of processor caches, and manipulation of external caches on
Macintosh models that incorporate these features. It also describes how
system software uses a memory management unit (when available) to implement
special caching options. Changes since October 1991. Described use of
AppleTalk Transition Queue event, ATTransSpeedChange, when altering the
68040 cache state on the fly. This call must be issued so that LocalTalk
can reevaluate its timers. Otherwise LocalTalk becomes disabled.

 Name  =  CMOS On LC PDS.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:CMOS On LC PDS.cpt
 Size:  4K         Date:10/29/92         Version:
 Description:
 CMOS On LC PDS - This Technical Note provides PDS card developers with some
important information about making PDS cards for the Macintosh LC. Due to
the way the Macintosh LC was designed, Apple strongly recommends that all
PDS cards be developed with CMOS parts.

 Name  =  C Glue.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:C Glue.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 C Glue - MPW 2.0 includes new C interfaces to ROM routines which no longer
do string and point conversions. These new interfaces are described here.

 Name  =  CDEF Params and Bugs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:CDEF Params and Bugs.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 CDEF Params and Bugs - This Technical Note describes known bugs in the
Control Manager which affect control definition functions ('CDEF'
resources). Changes since August 1988. Updated to reflect known bugs in the
posCntl and thumbCntl messages and the Control Manager _TrackControl call.

 Name  =  CD-ROM Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:CD-ROM Q&As.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 CD-ROM Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  C++ Pitfalls.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:C++ Pitfalls.cpt
 Size: 22K         Date:10/29/92         Version:
 Description:
 C++ Pitfalls - This Technical Note covers most of the common and serious
subtle problems that a MPW C++ user might encounter. For more information
consult the current C++ literature. This Note will be updated periodically
to reflect changes in the language and the compiler. Always read the
release notes included with the MPW C++ to find out the latest status for
known bugs and restrictions.

 Name  =  Bus Error Handlers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Bus Error Handlers.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 Bus Error Handlers - This Technical Note discusses bus errors and how
applications and drivers should deal with them. Changes since February
1991, Discussion of why declaration ROMs are necessary in NuBus™ design.
This discussion is important for those who are considering using a
workaround instead of declaration ROMs. Also added are some hints that you
should be aware of if you are planning to write a bus error handler for the
’040.

 Name  =  Bundles.cpt
 Path =  AMUG CD:Files:MacTechNotes:Toolbox:Bundles.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Bundles - A bundle is a collection of resources. Bundles can be used for a
number of different purposes, and are currently used by the Finder ito tie
an icon to a file type, allowing your application or data file to have its
own icon.

 Name  =  Break/CTS Serial Driver Eve.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:Break/CTS Serial Driver Eve.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Break/CTS Serial Driver Eve - This technical note documents the event
record information that gets passed when the serial driver posts an event
for a break/CTS status change. The serial driver can be programmed to post
a device driver event upon encountering a break status change or CTS change
(via the SerHShake call). The structure of device driver events is
driver-specific. This technical note documents the event record information
that gets passed when the serial driver posts a device driver event for a
break/CTS status change.

 Name  =  Borrowed AFP Sessions.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Borrowed AFP Sessions.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Borrowed AFP Sessions - This Technical Note shows how to borrow the session
reference number of an AFP volume mounted by the Macintosh File System. It
also shows how to retrieve other information from the file system for a
mounted AFP volume.

 Name  =  Boot Problems.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Boot Problems.cpt
 Size: 18K         Date:10/29/92         Version:
 Description:
 Boot Problems - The death of a hard disk with megabytes worth of data can
be exceedingly traumatic. This technical note will describe techniques for
recovering a hard disk and the data that is on it. The discussion will also
include some tips on how to avoid problems.

 Name  =  Boot Blocks.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:Boot Blocks.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Boot Blocks - There are two undocumented features of the Boot Blocks. This
note will describe how they currently work. Warning - The format and
functionality of the Boot Blocks will change in the future; dependence on
this information may cause your program to fail on future hardware or with
future System software.

 Name  =  Blessed Folder.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Blessed Folder.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Blessed Folder - This Technical Note describes how to determine which
folder on an HFS volume is the blessed folder, that is, the folder that
contains both the System file and the Finder. Changes since January 1986,
The information about how to find the "Blessed Folder" has been deleted
from this technical note. The FindFolder function can now be used to find
the "Blessed Folder" and is documented in Inside Macintosh Volume VI, pages
9-42 to 9-44. This note now includes information about how to bless a
folder to the new system folder.

 Name  =  BitMapToRegion.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:BitMapToRegion.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 BitMapToRegion - This Technical Note discusses the routine BitMapToRegion,
which converts a bitmap to a region, and is available in the 32-Bit
QuickDraw INIT and from Apple Software Licensing. Changes since October
1989. Added trap definitions for developers using the 32-Bit QuickDraw
version of this routine without the correct MPW include file.

 Name  =  Basic QuickDraw Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:Basic QuickDraw Q&As.cpt
 Size: 27K         Date:10/29/92         Version:
 Description:
 Basic QuickDraw Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Avoid Using Network Events.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Avoid Using Network Events.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Avoid Using Network Events - Future System software enhancements will not
support network events. This note gives hints on weaning your application
from the use of network events.

 Name  =  Available Volumes.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Available Volumes.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Available Volumes - Standard File lets the user select one file from any
available volume; it is sometimes necessary for an application to find
which volumes are present. This technical note gives the proper method of
accomplishing this. There is a little-noticed feature of the low-level file
manager call PBHGetVInfo which allows specification of a “volume index” to
select the volume.

 Name  =  Author Index.cpt
 Path =  AMUG CD:Files:MacTechNotes: Indexes:Author Index.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 Author Index - This index lists each author and the Technical Notes they
are responsible for.

 Name  =  Assembly Language _InitGraf.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Assembly Language _InitGraf.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Assembly Language _InitGraf - The Macintosh Programmer’s Workshop (MPW)
requires assembly-language programmers to allocate their own QuickDraw
global variables rather than use the default record as indicated in Inside
Macintosh.

 Name  =  Arbitr UseofAFPMisc.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:Arbitr UseofAFPMisc.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Arbitr UseofAFPMisc - This Technical Note discusses a scheme for
arbitrating the use of the afpMiscUserCommand and afpMiscUserWrite
AppleTalk Filing Protocol (AFP) commands. Inside Macintosh Volume V lists
two AFP command codes that are reserved for developers. They are
afpMiscUserCommand (call number 191) and afpMiscUserWrite (call number
254). Several developers have asked that Apple arbitrate the use of those
two AFP calls. This Technical Note describes our recommended solution.

 Name  =  AppleTalk Phase 2.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleTalk Phase 2.cpt
 Size: 18K         Date:10/29/92         Version:
 Description:
 AppleTalk Phase 2 - This Technical Note discusses the new features and
calls available with AppleTalk Phase 2. Changes since August 1989.
Incorporated the ClosePrep and CancelClosePrep transitions and the new
control calls to the .MPP driver.

 Name  =  AppleTalk Ov Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleTalk Ov Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 AppleTalk Ov Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  AppleTalk Interfaces.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleTalk Interfaces.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleTalk Interfaces - What you need to do in order to use high-level
AppleTalk routines depends upon the interfaces you are using. Some
differences are outlined below.

 Name  =  AppleTalk2.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleTalk2.cpt
 Size: 60K         Date:10/29/92         Version:
 Description:
 AppleTalk2 - This Technical Note discusses the new features of AppleTalk
available for system software version 7.0 and AppleTalk version 57. The new
features include support for the Flagship Naming Service and the AppleTalk
Multiple Node Architecture. We present the Multiple Node Architecture and
discuss the new calls available to applications. We also discuss the impact
of the new architecture on AppleTalk Device files (ADEVs), and the changes
necessary to make them multinode compatible.

 Name  =  AppleShare and Old Finder.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleShare and Old Finder.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleShare and Old Finder - A rumor has been spread that if you use a
pre-AppleShare Finder on a workstation to access AppleShare volumes, you
can bypass AppleShare’s “access privilege” mechanisms. This is not true.
Access controls are enforced by the server, not by the Finder. If you use
an older Finder, you are still prevented (by the server) from gaining
access to protected files and folders; however, you will not get the proper
user-interface feedback that you would if you were using the correct
Finder.

 Name  =  AppleShareable Applications.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleShareable Applications.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 AppleShareable Applications - Normally, applications on an AppleShare
server volume cannot be executed by more than one user at a time. This
technical note explains why, and tells how you can enable your application
to be shared.

 Name  =  AppleShare Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleShare Q&As.cpt
 Size: 21K         Date:10/29/92         Version:
 Description:
 AppleShare Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  AppleShare Limits.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleShare Limits.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleShare Limits - This Technical Note describes some machine-dependent
limits of current versions of AppleShare and AppleShare servers. The
following chart lists some current AppleShare limits which are based upon
the chosen server platform and memory configuration.  The limits which
otherwise might be present on a workstation are still in effect and are not
affected by the workstation being logged into an AppleShare server. These
limits will change in the future.

 Name  =  AppleShare Foreground Apps.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AppleShare Foreground Apps.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 AppleShare Foreground Apps - This technical note outlines the requirements
and restrictions of an AppleShare foreground application. This information
pertains to AppleShare versions 1.1 and newer. An AppleShare server
requires a dedicated Macintosh. The server, however, is implemented as an
interrupt-driven application that runs in the system heap of the server
machine. This allows the running of a concurrent or foreground application
that will live in the application heap of the server machine. An example of
a foreground application is LaserShare, the LaserWriter spooler available
from Apple.

 Name  =  AppleEvents Send to Self.cpt
 Path =  AMUG CD:Files:MacTechNotes:Interapplication Comm.:AppleEvents Send to Self.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 AppleEvents Send to Self - If an application suspends handling of an Apple
event which it sent to itself, the Apple Event Manager will return
errAETimeout as the result of the AESend call. The event was still sent
correctly, however, and the answer (if any) should appear later in the
reply descriptor. However, a problem in system software versions 7.0 and
7.0.1 prevents applications from getting the reply data.

 Name  =  Apple Event Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Interapplication Comm.:Apple Event Mgr Q&As.cpt
 Size: 13K         Date:10/29/92         Version:
 Description:
 Apple Event Mgr Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  Appearance Of Text.cpt
 Path =  AMUG CD:Files:MacTechNotes:Text:Appearance Of Text.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 Appearance Of Text - This technical note describes why text doesn’t always
look the way you expect depending on the environment you are in.

 Name  =  Allegro Common Lisp.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:Allegro Common Lisp.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Allegro Common Lisp - This Technical Note describes some known problems and
provides solutions to these problems for the Macintosh Allegro Common Lisp™
package which is available from Apple Computer, Inc.  You should note,
however, that although Apple acquired Coral Software and is selling
Macintosh Allegro Common Lisp, Apple is not currently distributing any
other products which had been developed or previously sold by Coral
Software.

 Name  =  Alias Mgr Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Alias Mgr Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 Alias Mgr Q&As - This Technical Note contains a collection of Q&As relating
to a specific topic—questions you’ve sent the Developer Support Center
(DSC) along with answers from the DSC engineers. While DSC engineers have
checked the Q&A content for accuracy, the Q&A Technical Notes don’t have
the editing and organization of other Technical Notes. The Q&A function is
to get new technical information and updates to you quickly, saving the
polish for when the information migrates into reference manuals.

 Name  =  Alias File.cpt
 Path =  AMUG CD:Files:MacTechNotes:Files:Alias File.cpt
 Size: 11K         Date:10/29/92         Version:
 Description:
 Alias File - ResolveAliasFile always presents the user identity dialog when
mounting remote volumes. This Technical Note offers an alternative
function, ResolveAliasFileMountOption, which uses the previously
undocumented FollowFinderAlias trap to resolve alias files only if their
target is on an already mounted volume. Also included is an IsAliasFile
routine for identifying alias files.

 Name  =  AddDrive DrvrInstall.cpt
 Path =  AMUG CD:Files:MacTechNotes:Devices:AddDrive DrvrInstall.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 AddDrive DrvrInstall - AddDrive, DrvrInstall, and _DrvrRemove are used in
the sample SCSI driver in the SCSI Development Package, which is available
from APDA. This Technical Note documents the parameters for these calls.
Changes since March 1, 1988. Updated the DrvrInstall text to reflect the
use of register A0, which should contain a pointer to the driver when
called. Also added simple glue code for DrvrInstall and DrvrRemove since
none is available in the MPW interfaces.

 Name  =  ATalk Retry Timers.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:ATalk Retry Timers.cpt
 Size: 10K         Date:10/29/92         Version:
 Description:
 ATalk Retry Timers - This Technical Note explains how to effectively use
timers and retry mechanisms of the various AppleTalk protocols to achieve
maximum performance on an internet.

 Name  =  AT Remote Access Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AT Remote Access Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 AT Remote Access Q&As - This Technical Note contains a collection of Q&As
relating to a specific topic—questions you’ve sent the Developer Support
Center (DSC) along with answers from the DSC engineers. While DSC engineers
have checked the Q&A content for accuracy, the Q&A Technical Notes don’t
have the editing and organization of other Technical Notes. The Q&A
function is to get new technical information and updates to you quickly,
saving the polish for when the information migrates into reference manuals.

 Name  =  ATP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:ATP Q&As.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ATP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ASP & AFP.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:ASP & AFP.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 ASP & AFP - The descriptions of the AppleTalk Session Protocol and
AppleTalk Filing Protocol functions within the body of the AppleTalk
Manager chapter are incorrect and conflict with those in the Summary of the
AppleTalk Manager. This technical note resolves the discrepancy. The
descriptions of the AppleTalk Session Protocol and AppleTalk Filing
Protocol functions which are described on pages 534 through 548 of Inside
Macintosh Volume V conflict with the descriptions in the Summary of the
AppleTalk Manager section, pages 554 through 559.

 Name  =  AFP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:AFP Q&As.cpt
 Size:  6K         Date:10/29/92         Version:
 Description:
 AFP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  AFE Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:AFE Q&As.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 AFE Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ADSP Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Networking:ADSP Q&As.cpt
 Size:  8K         Date:10/29/92         Version:
 Description:
 ADSP Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  ADB Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:ADB Q&As.cpt
 Size: 16K         Date:10/29/92         Version:
 Description:
 ADB Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  A5 in GrowZone Procs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:A5 in GrowZone Procs.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 A5 in GrowZone Procs - If you have a grow zone function, it may get called
when a system routine is trying to allocate memory. Because this can
happen, you can’t be guaranteed that register A5 will be correct. If your
grow zone function depends on A5, you should save register A5, load A5 from
the low-memory global CurrentA5 (a long word at $904), and restore the
caller’s A5 before you exit.

 Name  =  A5 and Patching traps.cpt
 Path =  AMUG CD:Files:MacTechNotes:Overview:A5 and Patching traps.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 A5 and Patching traps - Future software may allow desk accessories to have
their own globals by changing register A5 when the accessory is entered and
exited. This can cause problems for applications that patch traps without
following certain rules.

 Name  =  A/UX  System Calls.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:A/UX  System Calls.cpt
 Size: 21K         Date:10/29/92         Version:
 Description:
 A/UX  System Calls - This Technical Note discusses how to make A/UX system
calls from applications developed in the Macintosh environment.  This is
useful to anyone porting an existing Macintosh driver or application to
work on A/UX as well. Changes since August 1990. Added information about
how to make use of fork() system calls under MultiFinder, as well as how
various A/UX system calls behave under the MultiFinder emulation mode.

 Name  =  A/UX Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:A/UX Q&As.cpt
 Size: 25K         Date:10/29/92         Version:
 Description:
 A/UX Q&As - This Technical Note contains a collection of Q&As relating to a
specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  A/UX Compatibility Guide.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:A/UX Compatibility Guide.cpt
 Size: 12K         Date:10/29/92         Version:
 Description:
 A/UX Compatibility Guide - This Technical Note describes details of the
A/UX 2.0 implementation of which developers should be aware, so that their
Macintosh applications also work properly under A/UX. Changes since April
1989. This Note formerly described A/UX 1.1 Toolbox Bugs, but has been
completely rewritten to cover A/UX 2.0 compatibility. Changes since June
1990. Changes due to A/UX 2.0.1, also added some new important issues.

 Name  =  A/ROSE Q&As.cpt
 Path =  AMUG CD:Files:MacTechNotes:Platforms & Tools:A/ROSE Q&As.cpt
 Size: 15K         Date:10/29/92         Version:
 Description:
 A/ROSE Q&As - This Technical Note contains a collection of Q&As relating to
a specific topic—questions you’ve sent the Developer Support Center (DSC)
along with answers from the DSC engineers. While DSC engineers have checked
the Q&A content for accuracy, the Q&A Technical Notes don’t have the
editing and organization of other Technical Notes. The Q&A function is to
get new technical information and updates to you quickly, saving the polish
for when the information migrates into reference manuals.

 Name  =  32-Bit QuickDraw V1.2.cpt
 Path =  AMUG CD:Files:MacTechNotes:Imaging:Graphics:32-Bit QuickDraw V1.2.cpt
 Size:  9K         Date:10/29/92         Version:
 Description:
 32-Bit QuickDraw V1.2 - This Technical Note describes the changes and
enhancements to 32-Bit QuickDraw from version 1.0 (as shipped on the
original Color Disk) to version 1.2, which ships with System Software 6.0.5
and later.  This Note assumes familiarity with Inside Macintosh, Volume V,
Color QuickDraw, and 32-Bit QuickDraw release notes.

 Name  =  21" RGB Specs.cpt
 Path =  AMUG CD:Files:MacTechNotes:Hardware:21" RGB Specs.cpt
 Size:  7K         Date:10/29/92         Version:
 Description:
 21" RGB Specs - This Technical Note presents the technical specifications
for the Macintosh 21" Color Display with the objective of allowing display
board and accelerator board manufacturers to ensure compatibility with this
monitor.

 Name  =  128K ROM/Asm.cpt
 Path =  AMUG CD:Files:MacTechNotes:Memory:128K ROM/Asm.cpt
 Size:  5K         Date:10/29/92         Version:
 Description:
 128K ROM/Asm - When calling MaxApplZone and MoveHHi from assembly language,
be sure to get the correct code. MaxApplZone and MoveHHi were marked [Not
in ROM] in Inside Macintosh, Volumes I-III . They are ROM calls in the 128K
ROM. Since they are not in the 64K ROM, if you want your program to work on
64K ROM routines it is necessary to call the routines by a JSR to a glue
(library) routine instead of using the actual trap macro. The glue calls
the ROM routines if they are available, or executes its copy of them
(linked into your program) if not.